06-11-2010
10 More Discussions You Might Find Interesting
1. Solaris
Hello all,
I want to run a script every 3 minutes in os level and to send mail.
I scheduled in crontab as
3 * * * * /mnt1/monitorscripts/testdbstart.sh
I got mail every one hour and I confirmed that the script is running every 1 hour which doesn't meet my requirment.
Where I am... (4 Replies)
Discussion started by: prashanth_gs
4 Replies
2. UNIX for Dummies Questions & Answers
I have the following crontab entry.
0,30 00-16 * * *
This job runs every 30 minutes between the hours of 12:00AM and 4:00PM. How can I have it stop at 4:30PM instead?
Thank you,
David (3 Replies)
Discussion started by: dkranes
3 Replies
3. UNIX for Dummies Questions & Answers
i have set the below one in cronta, expecting that it would run every fourth saturday for Jan, Apr, Jul and Oct,
but it comes out that it run everyday between 21 to 27.
Please help!!
00 01 21-27 1,4,7,10 6 my_job (1 Reply)
Discussion started by: boydunshout
1 Replies
4. Shell Programming and Scripting
I have a script which shoud run after every 30 minutes.Though I know abt crontab, unfortunately I dont have access/authorization to use crontab in my terminal.
Could any one pls let me know how to schedule the script without crontab ?
Regards
Prashant:) (3 Replies)
Discussion started by: prashant43
3 Replies
5. Shell Programming and Scripting
I would like to execute my script at 17.30 and 23.00 using crontab, could anybody help me out!!
Thanks in Advance!! (1 Reply)
Discussion started by: jatanig
1 Replies
6. Shell Programming and Scripting
Hi,
I have a script which will query the DB and added to crontab at 1,2,6,7 AM everyday and sends a email if count is 0.
Now the problem is, if crontab is disabled it doesn't sends a mail.
Please tell me how can I handle this situation in the script. (2 Replies)
Discussion started by: sandy1028
2 Replies
7. UNIX for Advanced & Expert Users
All,
I'm a newbie with crontab and I need your help with schedule a cold-backup running every Sunday at 7am except 1st of the month.
Thank you so much. (2 Replies)
Discussion started by: hanie123
2 Replies
8. Shell Programming and Scripting
Hi,
My script is in $home/bin/sample.sh.
I want to run the script for 3times a day,
first execution will be at 08:00 am.
second execution will be at 16:00 pm
third will be at 23:59 pm.
what will be the entry with this requirement?? (1 Reply)
Discussion started by: shrima.pratima
1 Replies
9. Shell Programming and Scripting
Hi all,
I would like to schedule a crontab script, which should run From 8pm Thursday to 2am Friday and it should run every 10 minutes. I have put a script like below, is it the correct one.
10 01,02,20,21,22,23,00 * * 4-5 /u01/app/test.ksh
Any other options available to schedule the same... (6 Replies)
Discussion started by: sid2013
6 Replies
10. Shell Programming and Scripting
Hi All,
How to schedule crontab on all day except sunday and monday means from tuesday to saturday at 06:00AM. (3 Replies)
Discussion started by: Riverstone
3 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)