04-05-2005
Rather than the long process list check, why not use a lock file and check for its existence? ie, if it exists, there's another process running, so don't run. Just be sure to include a trap for removing the file for all termination possibilities:
trap 'rm -f $LOCKFILE' 0 1 2 3 13 14 15
Cheers,
Keith
10 More Discussions You Might Find Interesting
1. Solaris
I am trying to setup cronjob and once I start to save it is not working. This is what I am getting after I executed crontab -e, I am not even getting the privious entry and I am running from root.
crontab -e
421
10 3 * * * /usr/sbin/logadm
?
:wq
?
Why is it not saving? Any input is... (4 Replies)
Discussion started by: mokkan
4 Replies
2. Solaris
new to unix here, im learning how to schedule jobs with crontab. The following cron job runs under root but not under a test account i created.
50 11 * * 0 /usr/bin/banner "HELLO" > /dev/console
i have no idea with it isn't running under the test account but runs right on time when i create... (7 Replies)
Discussion started by: solne
7 Replies
3. UNIX for Dummies Questions & Answers
Hey all.
Im totally new with makeing websites ect
The thing is, i wanted to make one of those pimp games, so i installed a script called mypimpscript.. it works but the 10mins cron jobs dont...
ive tried to set it up in cpanel, but im doing it wrong :S
right now it looks like this php... (1 Reply)
Discussion started by: princess
1 Replies
4. Shell Programming and Scripting
Hello All,
I want to run a script for every 5 minutes interval.So i developed a script which has to be scheduled to run for every 5 minutes. That script internally runs another script. But the problem is it is not executing properly. Can anybody throw some light on this.
Below are the code... (4 Replies)
Discussion started by: RSC1985
4 Replies
5. UNIX for Dummies Questions & Answers
I have created a cron job for the vtiger workflow to execute the shell file named com_vtiger_workflow.sh to run the workflow.
I've created the following line in crotab -e :
00 13 * * * /var/www/html/prashant/cron/modules/com_vtiger_workflow/com_vtiger_tiger_workflow.sh | mail -s 'Check... (2 Replies)
Discussion started by: anaigini45
2 Replies
6. Shell Programming and Scripting
Hi ,
I have a TCL script which i am supposed to run as a cron job..
The script works fine from command line , but when run as a cron job , its unable to find a package,,
my crontab is as follows.
---------------------------
#!/usr/bin/ksh
* * * * * PATH=/cm8/auto/Automation/Library/TclLib
... (7 Replies)
Discussion started by: Sudharshana
7 Replies
7. UNIX for Dummies Questions & Answers
Hey guys... first post here...
I have set up the following cron to create daily backups for me and rotate them weekly:
date=`date +%d`; tar -zcvf /home/mysite/backups/backup_dev_$date.tgz /home/mysite/public_html/dev/app --exclude=/home/mysite/public_html/dev/app/tmp
However, I keep... (4 Replies)
Discussion started by: Crazy Serb
4 Replies
8. UNIX for Dummies Questions & Answers
I have a perl script which Im planning to run every minute.
I have set the cron job as
* * * * * PATH= /usr/local/bin:/usr/bin:/usr/sbin:/usr/lib; perl /dm2/www/html/isos/pre5.3/autoDownload.pl
I assume the script is executing every minute only because I see a entry like below when I do... (2 Replies)
Discussion started by: srijith
2 Replies
9. Solaris
When i am trying to open crontab throught command crontab -e. It is not opening?
OUTPUT:
# crontab -e
sh: vim: not found
The crontab file was not changed.
Please let me know how to open and edit it??? (10 Replies)
Discussion started by: kkalyan
10 Replies
10. Shell Programming and Scripting
HI,
I have written an executable file in unix and I was able to execute it successfully but when I called this file with cron job it was giving error like "permission denied" and "No such file or directory".
Please help in how cron calls the file and what permission is required on the file... (2 Replies)
Discussion started by: vipin kumar rai
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)