|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
SCO 5.0.7 Cron creates files with 600, need 644
Post 302279004 by 65bit on Wednesday 21st of January 2009 05:53:26 PM
01-21-2009
SCO 5.0.7 Cron creates files with 600, need 644
Hi,
I've searched and read, and searched and read some more; but I'm still not connecting the dots or understanding what I need to change.
I have a script that creates a file. If I run it as root, the file gets created with 644 permissions like I want. That seems to make sense (at least I think
), as when I type umask, it returns 022. So, new files would be created with 666, but the 022 umask is being applied against it and resulting in a file with 644.
However, if I run it from cron, the file gets created as 600. Like there is an 066 umask being applied against it. Is it simply that there's a different umask in force for files created by cron? If so, where would I find and edit it?
Or is it a matter of the permissions on crontab itself? The one in /usr/bin and /ibin are both owned by root, with a group of root and both have 777 permssions.
There's a lot of info out there on cron jobs and permissions, but most seems centered around the cron job not running. Mine runs, it's just creating files with different permissions than I.
Any input is appreciated.
Thanks,
David
I've searched and read, and searched and read some more; but I'm still not connecting the dots or understanding what I need to change.
I have a script that creates a file. If I run it as root, the file gets created with 644 permissions like I want. That seems to make sense (at least I think
), as when I type umask, it returns 022. So, new files would be created with 666, but the 022 umask is being applied against it and resulting in a file with 644.However, if I run it from cron, the file gets created as 600. Like there is an 066 umask being applied against it. Is it simply that there's a different umask in force for files created by cron? If so, where would I find and edit it?
Or is it a matter of the permissions on crontab itself? The one in /usr/bin and /ibin are both owned by root, with a group of root and both have 777 permssions.
There's a lot of info out there on cron jobs and permissions, but most seems centered around the cron job not running. Mine runs, it's just creating files with different permissions than I.
Any input is appreciated.
Thanks,
David
|
|
6 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hey folks,
I have used gVim in Windows for many years but I have never found an answer to a very simple question I am going to ask you guys...
My question is if there is a way to eliminate the creation of those ~ files that gVim creates in Windows. If you have ever used gVim in Windows you... (2 Replies)
Discussion started by: ghbarratt
2 Replies
2. Shell Programming and Scripting
Hi,
i have 600 or more file on my server and from this 600 files i want to make one file. i have written this script
SPATH=/etlstg/DAT
TPATH=/etlstg/DAT/DAT_PROCESSED
FILE_DATE=`TZ=CST+24 date +20%y%m%d`
a1=0
while
do
a2=0
while
do
a3=0
while
... (1 Reply)
Discussion started by: prasson_ibm
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
This is my first time on this forum..
I searched the previous answers, but didn't find the answer I was looking for at first glance.
csplit works beautifully for me, except for one thing. My file looks like this:
ad|name1|asdf...(several pages)..asdf ...
ad|name2|asdf...(several... (8 Replies)
Discussion started by: juliette salexa
8 Replies
4. UNIX for Advanced & Expert Users
In our project we have several unix scripts that trigger different processes. These scripts write logs to a particular folder 'sesslogs', create output data files in a separate directory called 'datafiles' etc. Usually L1 support team re-run these scripts . We donot want L1 support team to have... (14 Replies)
Discussion started by: waavman
14 Replies
5. AIX
Hi,
We are using AIX machines. How to create all files generated in a directory with 644 permissions automatically.
Regards,
Suresh (11 Replies)
Discussion started by: suresh3566
11 Replies
6. Shell Programming and Scripting
I want to crop an image and am using convert
convert mountain.png -crop 3000x4500 +repage -format png mountain--cr.png
The problem is that convert is creating 4 files
mountain--cr-0.png
mountain--cr-1.png
mountain--cr-2.png
mountain--cr-3.png
The first is what I need, the other... (10 Replies)
Discussion started by: Kangol
10 Replies
LEARN ABOUT SUSE
crontab
CRONTAB(1) General Commands Manual CRONTAB(1) NAME
crontab - maintain crontab files for individual users (ISC Cron V4.1) SYNOPSIS
crontab [-u user] file crontab [-u user] [-l | -r | -e] DESCRIPTION
Crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their own crontab, and though these are files in /var, they are not intended to be edited directly. If the cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the cron.allow file does not exist but the cron.deny file does exist, then you must not be listed in the cron.deny file in order to use this command. If neither of these files exists, only the super user will be allowed to use this command. If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse crontab and that if you are running inside of su(8) you should always use the -u option for safety's sake. The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given. The -l option causes the current crontab to be displayed on standard output. The -r option causes the current crontab to be removed. The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. SEE ALSO
crontab(5), cron(8) FILES
/etc/cron.allow /etc/cron.deny STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line. AUTHOR
Paul Vixie <vixie@isc.org> 4th Berkeley Distribution 29 December 1993 CRONTAB(1)