06-24-2005
as long as the job is applicable and the paths to the executables are the same, you should be able to copy and/or move cron jobs anywhere
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi folks,
I need an explanation on cron jobs with an example (4 Replies)
Discussion started by: vijaysabari
4 Replies
2. UNIX for Dummies Questions & Answers
I was wondering if itīs possible to cron job not to run on a certian day and time. Iīve got a job that runs everyday at 08:00
but would like it not to run on the 20:th between 08:00 and 10:00
Anyone know if this is possible, and if. How do i do it?
regards...
dOzY (3 Replies)
Discussion started by: dozy
3 Replies
3. UNIX for Dummies Questions & Answers
Where can someone find info on Cron Jobs? Very new to UNIX and the PC I inherited looks to have several of them. Looks like they are some kind of background program that runs automatically at specified times. Would like to delete some of them and know more about them. (6 Replies)
Discussion started by: dereckbc
6 Replies
4. UNIX for Advanced & Expert Users
I need to monitor my cron jobs with another unix machine since occasionally the cron will go down on the main server but there are no errors. Can anyone help with a script to write to use the cron on the back up machine to monitor the main server?
I am using SCO and the cron jobs have been... (3 Replies)
Discussion started by: rmarral
3 Replies
5. Linux
I created a php script.
I'd like to have it run as a cron job every day at 10:30am. So i added
30 10 * * * /script.php to the cron file
Is it possible to run the script on the command line to test it out ? (1 Reply)
Discussion started by: dannyd
1 Replies
6. Solaris
how to Put a cron entry which should be same script triggered on every Saturday and 1st of every month at 01.00 GMT.
0 2 1 * 6 --( At 2.00 GMT every sat & on 1st of every month)
the above syntax is correct?
Thanks (1 Reply)
Discussion started by: kurva
1 Replies
7. Linux
Hi,
I am a Linux administrator (newbie) in my company. The distro being used in the servers here is Centos 5.3
Just need to know, as a Linux administrator is it better for me to use /etc/crontab to set my cron jobs. I do not want to use the crontab -e to schedule my cron jobs.
That means... (1 Reply)
Discussion started by: anaigini45
1 Replies
8. Shell Programming and Scripting
Hi Frenz,
How do we get a cron job running in background to foreground ? (3 Replies)
Discussion started by: mkalase
3 Replies
9. Solaris
There are two jobs in Solaris , Cron and at jobs..
I know how to disable or enable cron jobs.
How can I enable at jobs and disable it.
Kindly help.
Rj (2 Replies)
Discussion started by: jegaraman
2 Replies
10. Shell Programming and Scripting
Hi
I am new to submitting jobs. I am trying to submit my perl file to the cluster.
This is what my shell file looks like (shell1.sh):
#!/bin/sh
#$ -S /bin/sh
cd data/projects/mydir/abbc
perl autocorro.pl
followed by qsub shell1.sh
It takes the qsub, but does nothing. I check... (1 Reply)
Discussion started by: theawknewbie
1 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)