Conference humane::scheduler

1135.0. "d-unix sched, logfile protections" by CSC32::H_SO (Redline? What redline?) Wed Jul 24 1996 17:01

    Hi.
    
    I needs some help from folks with littel more experience with
    d-unix Scheduler v3 than I have (wouldn't take much, really)
    
    I've got a customer complaining that he has two problems where 
    Scheduler is creating files with inappropriate protections:
    
     1. Several files installed by scheduler v3.0-2 have o+w:
    
            [...]
            POLYCENTER Scheduler V3.0 Client for Digital UNIX V3.2
            Digital UNIX POLYCENTER Scheduler V3.0 Client IVP has executed
    		successfully
            root@java> cd /var/sched
            root@java> ls -l
            total 18179
            -rwxrwxrwx   1 root     system    105007 Dec 15 07:27 README
            [...]
            -rwxrwxrwx   1 root     system   1476372 Dec 15 07:27
    		sched_help_profile.decw_book
            [...]
    
        This occurred on all five systems I installed on.
        Workaround to 'chmod -R o-w /var/sched'.
    
     2. Log files created by scheduler default to a+w:
    
            sxkac@moka> rm date.log*
            rm: date.log*: No such file or directory
            sxkac@moka> schedule run job moka_date
             SCHED-I-JOBRUNREQ, Job Run requested for MOKA_DATE(462)
            sxkac@moka> ls -l date.log*
            -rw-rw-rw-   1 sxkac    system       643 Mar 22 12:39 date.log
            -rw-rw-rw-   1 sxkac    system         0 Mar 22 12:39 date.log.err
    
        Workaround is to pre-create logs with appropriate protections, but many
        users don't bother.
    
    Are these protections normal/expected?  Are there any other workaround
    for this behavior?
    
    Thanks.
    
    Jay