01-03-2007
Write a script that checks the current time, sleeps for 15minutes and then starts the processes, then save it in /etc/rc3.d/S99sleepingjob
Each time the server reboots it will run this script.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am a total newbie to all things Unix. I've worked out I need to set up something that will allow me to automatically backup a DB for me, the DB is for a foum system I run.
Now, I've only found out I need to use telnet for this, and worked out hwo to log into telnet today. From here... (4 Replies)
Discussion started by: eludlow
4 Replies
2. 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
3. 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
4. UNIX for Dummies Questions & Answers
Hi,
We have a group of hosts using which the cron jobs are submitted...
Few days ago i had submitted a cron job in of these hosts, but unfortunately forgot the host name :(
Can anyone please help me out in finding this host name from which the cron s submitting the job, i dont want the... (2 Replies)
Discussion started by: bhavanisree
2 Replies
5. 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
6. 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
7. Shell Programming and Scripting
Hi,
please help on this am trying to exec the below mentioned cron jobs
but its getting failed fro the past two days
###but when am trying to execte the cron by the times
23,29 18 * * * /export/home/inrvgo/thelak/China.sh
its getting exec properly
please help on this
#... (8 Replies)
Discussion started by: thelakbe
8 Replies
8. 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
9. Red Hat
I'm running cronjobs on a redhat 5.X. Cronjobs are getting failed frequently so how to find the root cause (2 Replies)
Discussion started by: karthik9358
2 Replies
10. Shell Programming and Scripting
How to see which cron jobs are not running? (2 Replies)
Discussion started by: rahul.raj1989
2 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if
time has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO
crontab(1), crontab(5), pam(8)
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)