11-04-2004
cron user
# cd /usr/lib/cron/
# ls
at.deny cron.deny FIFO logchecker queuedefs
I noticed I do not have a cron.allow file.
I have entries in the crontab file and users listed in the at.deny cron.deny files
# more at.deny
daemon
bin
smtp
nuucp
listen
nobody
noaccess
If I wanted to set a cron job, do I have to create a cron.allow file and how does it choose the user, by who submits thew job I suppose?
I have a script that is run by oracle user to create a backup that I would like to cron.
do I:
log in as oracle, edit crontab (crontab -e)
enter - 10 0 * * * /export/home/oracle/path_to_script/script.ksh
(run 00:10 am every night.)
then I'm done?
oracle owns the script.
or do I have to create a cron.allow file and add oracle to it?
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a command that is found in /usr/ud51/bin called stopudt which safely stops idle database users (let's writes finish, etc).
If I login as root and issue stopudt the process is stopped.
I put a script in cron to run it and it says stopudt not found.
/usr/ud51/bin is in root's PATH. ... (10 Replies)
Discussion started by: michieka
10 Replies
2. HP-UX
hi all,
i have one account for unix Tru64.
i can login this account and i do execute special shell script(login sqlplus, execute another shell, etc... ) on this account on my server.
but i can't run this shell from cron tab.
i think that become cron user envirnoment variables. (3 Replies)
Discussion started by: Tlg13team
3 Replies
3. Shell Programming and Scripting
Hello all,
I have solaris 10. I have have a script that installs crontab for a user. I want to add some more features to this script.
I want to check whether the user exists in etc/cron.d/cron.allow ... if yes then continue the script without adding .... if not, then add that user to the... (6 Replies)
Discussion started by: MisterKhan
6 Replies
4. HP-UX
Hi there,
I have a small script that I need to run every hour and would like to schedule this a a cron job. I have tried running it in root but due to elm not being setup and file permissions it does not work unless it is ran from a specfic account. Is it possible to setup a user cron and how... (5 Replies)
Discussion started by: lodey
5 Replies
5. Solaris
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
Discussion started by: ksvaisakh
5 Replies
6. Solaris
Hi,
Should the user jobs specified in crontab be running in background?
Cron daemon is already running in background. So I am not sure
whether should the jobs (output and error messages are redirected to file)
ran by it be explicitly stated to be run in background (& at end of command)
if one... (1 Reply)
Discussion started by: joe_x
1 Replies
7. Shell Programming and Scripting
Suppose user 'asdf' is not logged into server 'bbbb', but the server is up. User 'asdf' has cron job. Will it be executed? (1 Reply)
Discussion started by: thulasidharan2k
1 Replies
8. Solaris
I have noticed this error in /var/cron/log:
> CMD: /usr/lib/acct/ckpacct
> adm 6739 c Tue Oct 11 10:00:00 2011
< adm 6739 c Tue Oct 11 10:00:00 2011 rc=1
! bad user (adm) Tue Oct 11 11:00:00 2011but when I try to list crontab of user 'adm':
solarni/~# crontab -l adm
crontab: you are... (4 Replies)
Discussion started by: orange47
4 Replies
9. Shell Programming and Scripting
There is a program that we (a company I'm working for) would like to run once per day, and the approach we're taking is to create a fake user to give a location to the data for this program, and to be the user running the program. For the sake of the discussion, let me call the fake user "bob".
... (5 Replies)
Discussion started by: stevendaryl
5 Replies
10. UNIX for Dummies Questions & Answers
Hi,
i have question about cron. can we have user based cron file under /var/spool/cron or we should have only root file which can only be accessed by root user or admin and he should only be doing the task of scheduling.
PKS (8 Replies)
Discussion started by: praveenkumar198
8 Replies
LEARN ABOUT OPENSOLARIS
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.11 1 Mar 1994 queuedefs(4)