Workload Automation

Expand all | Collapse all

Autosys R11.0 vs 4.5  umask differences - how to set  on R11

Jump to Best Answer
  • 1.  Autosys R11.0 vs 4.5  umask differences - how to set  on R11

    Posted 02-13-2013 12:59 PM
    We are currently converting from Autosys 4.5 agent to R11.0 SP5 agents. We have found a difference in the default umask depending on which version of autosys is used to launch a batch job.

    If you create a simple script on a linux server to touch a file, the default permissions are different based on version launching the job. The default umask for 4.5 will be 002, on R11 it will be 022. Since the 4.5 agent is launched via great grand daddy init, it is inheriting it's default umask of that process. We validated great grand daddy init has a umask of 002 which fits. However, since R11 is a daemon running in the background, we are presuming the default umask is matching that of root's default since it's root that starts the process on the server. But we are not sure.

    Has anyone else run into this - is there a way to specify what the daemon's default umask is OR what files default permission are when they are created. Or are we correct in our assumption and there really isn't a way to fix it except change roots default (yuck).

    Thanks


  • 2.  RE: Autosys R11.0 vs 4.5  umask differences - how to set  on R11

    Posted 02-13-2013 05:58 PM
    you can put umask command right into agent start-up script, which the new daemon.


  • 3.  RE: Autosys R11.0 vs 4.5  umask differences - how to set  on R11
    Best Answer

    Posted 02-13-2013 06:16 PM
    We have isolated the problem

    The major difference between Autosys 4.5 and R11 is how the jobs are launched. With 4.5, Autosys is a service that is launched by the internet daemon init (just like telnet, ftp, rsh, etc). The autosys process then execs the batch job requested and off he goes. With Autosys R11, an Autosys daemon is running on the server. When a batch request is sent to the daemon, it does a fork and exec to launch the batch job requested.

    On certain servers the xinetd.conf, the umask is not consistent with bashrc (and the other shell files). On these machines, the umask is set to 002 which we believe causes the auto_remote jobs to inherit this setting. However, the R11 auto_remote does not use xinetd.conf. We presume it gets its values in the same manor as anyone else who signs on to the machine i.e. 0022 instead of 002. RedHat 4 machines do not have a umask value in the xinetd.conf. Consequently, we believe r11 and r4.5 will behave the same on these devices.

    So, one option we are exploring is modification of the auto.profile to force the umask to match what's in the xinitd.conf file.