Board index Sco Unix

Environment for jobs run out of root cron

Environment for jobs run out of root cron

Post by Steven J. Hat » Thu, 14 Nov 1996 04:00:00



We're encountering some problems setting the umask on files created by
cron jobs run out of the root cron.(SCO 5) Files created come out as
read/write by root, but closed for group and other.

root's environment seems to be set correctly, /usr/lib/cron/.proto and
.proto.b seem to be OK. Man pages don't seem to be providing any
clues.

Can someone tell me where this environment is set, and how/where I can
modify it? TIA

--------------------------------
Steven J. Hatle
Systems Administrator
Tires Plus Groupe

I'm not allowed to drive the train, the whistle I can not blow
I'm not allowed to say how far the train can go
I'm not allowed to let off steam, or even clang the bell,
But let the damn thing jump the track and see who catches hell
(stolen from James_T_Ranks)
--------------------------------

 
 
 
Top

Environment for jobs run out of root cron

Post by Bill Vermilli » Wed, 20 Nov 1996 04:00:00




Quote:>We're encountering some problems setting the umask on files created by
>cron jobs run out of the root cron.(SCO 5) Files created come out as
>read/write by root, but closed for group and other.
>root's environment seems to be set correctly, /usr/lib/cron/.proto and
>.proto.b seem to be OK. Man pages don't seem to be providing any
>clues.
>Can someone tell me where this environment is set, and how/where I can
>modify it? TIA

If the environment variable aren't too big you could set them
on the cron line and put the cron command and variables in
parentheses.

--


 
 
 
Top

1. Q. What defines the Environment variables when a users cron job runs ?

When a user creates a script for scheduled execution as a cron job,
what controls the environment variables for the shell running the
script ?

For instance, are the normal /etc/profile and $HOME/.profile files
used or must every environment variable be defined in the script
itself ?

Of obvious importance is the $PATH variable, which will determine
whether the program files used in the script can be found, if the full
file path has not been given.

Thanks in advance

John Auld

2. Error 0x01 and VFS: Kernel Panic on ThinkPad

3. cron did not run root jobs (solaris 2.5.1)

4. Auto Logout

5. Cron jobs running as something other than root

6. restarting stopped processes

7. Root fails to run cron job

8. EZMLM in combination with qmail

9. Cron jobs running as something other than root

10. Cron <root@host> run-parts /etc/cron.daily

11. Postinstallation - Cron <root@main> run-parts --report /etc/cron.daily

12. Cron <root@host> run-parts /etc/cron.weekly

13. Cron <root@cxXXXXX-a> run-parts /etc/cron.daily


All times are UTC
Board index