" You can execute crontab if your name appears in the file /usr/lib/cron/cron.allow. If that file does not exist, you can use
crontab if your name does not appear in the file /usr/lib/cron/cron.deny.
If only cron.deny exists and is empty, all users can use crontab. If neither file exists, only the root user can use crontab. The allow/deny files consist of one user name per line. "
Hello:
If I want to run a crontab every hour between 9 am to 9pm, will this work
00 09-19 * * * /.../.../../program.sh
If the above does not work, what should it be ??
Thanks, ST2000 (4 Replies)
I have a script that is being called from cron job .
This script further call 3 scripts which runs in the background .
main script ( called from cron )
{
script1 &
script2 &
script3 &
}
How to know when the main script is over ?? (3 Replies)
need help to write crontab
my crontabe file every minute to rsh and check that it is running or not
i want to change it on every 1o minute please help me
example of my crontab
#check if system is running
* * * * * rsh metal3 /users/test/run.server
i want to check that every 10... (2 Replies)
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Hi All
I have a requirement to schedule my script through cron tab.
I have 2 scripts to schedule.
Case1:My script should run every day in the server.It should be triggered in every 2 mins interval.i.e suppose i implemented the script now my script should run every 2 mins.How can i... (6 Replies)
Hi All,
I am required to make a crontab entry, I have the below requirement:
1. It should execute at 06:15 12:00 and 18:30
2. It should execute every day of the month for all the 30 days
I am going to add the below entry in the crontab file.
15,0,30 6,12,18 * * 0-6 cd... (3 Replies)
Hi
In my Unix server more than 500 cron jobs are scheduled daily and weekly basics.
Now,I would like to know only list of JOBs,which are running only on 14th of every month?
How can i find only which are all jobs will be scheduled only on 14th.
Please tell me the script. (4 Replies)
Hi,
We have a couple of jobs are scheduled in CRONTAB.
Now. I want generate a report for each job how many times ran successful and failed in a 1 month of time period.
is there any way to find in CRONTAB.
Please advise on this. (1 Reply)
Hi,
I have a cron tab file , which executes a particular script in a scheduled time and creates a output file. Since the cron tab file was created by the root , there is no access permission( for the output files) for other users irrespective of the default directory permission on which the... (5 Replies)
Discussion started by: BalajiUthira
5 Replies
LEARN ABOUT OPENDARWIN
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)