SCO 5.0.7 Cron creates files with 600, need 644 Post: 302279004

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

Registered User

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 Smilie

), 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

65bit

View Public Profile for 65bit

Find all posts by 65bit

6 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

gVim creates and leaves strange tilde ~ files in Windows

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. Shell Programming and Scripting

write script for more then 600 files

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 ...

3. UNIX for Dummies Questions & Answers

naming files that csplit creates

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...

4. UNIX for Advanced & Expert Users

Allow user without dir write permission to execute a script that creates files

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...

5. AIX

How to create all files generated in a directory with 644 permissions?

Hi, We are using AIX machines. How to create all files generated in a directory with 644 permissions automatically. Regards, Suresh

6. Shell Programming and Scripting

Convert creates multiple files

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...

LEARN ABOUT X11R4

queuedefs

queuedefs(4)							   File Formats 						      queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and cron

SYNOPSIS

       /etc/cron.d/queuedefs

DESCRIPTION

       The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

	      q.[njobj][nicen][nwaitw]

       The fields in this line are:

       q	The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs  started  by  batch  (see
		at(1)); c is the default queue for jobs run from a crontab(1) file.

       njob	The  maximum  number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
		njob jobs will be run, and the others will be run as jobs that are currently running terminate.  The default value is  100.

       nice	The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user.  The default value is 2.

       nwait	The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in  that  job's
		queue, or because the system-wide limit of jobs executing has been reached.  The default value is 60.

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       Example 1: A sample file.

       #
       #
       a.4j1n
       b.2j2n90w

       This  file  specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
       of 1.  As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before  trying
       again to run it.

       The  b  queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2.  If a job
       cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All	other  queues  can
       have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
       are running cron will wait 60 seconds before trying again to run it.

FILES

       /etc/cron.d/queuedefs	       queue description file for  at, batch, and  cron.

SEE ALSO

       at(1), crontab(1), nice(1), cron(1M)

SunOS 5.10							    1 Mar 1994							      queuedefs(4)