04-09-2011
if it works in command line but not when scheduled in crontab, it is more than likely an environment issue.
Make sur you load the required environment variable from within your script.
(or a make script that load the environment variable and then launch th python pgm within that environment )
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
How can I configure cron file , to execute a script on evey alternate saturdays ?
I am using AIX 5.0 machine
Thanks in advance
Shihab (1 Reply)
Discussion started by: shihabvk
1 Replies
2. UNIX for Dummies Questions & Answers
hello there,
i'm learning about task scheduling with cron and all seems hyper exciting, yeppie. But there is a prob:
assume i have a script that needed to be executed at 7am everyday. I could do:
vi mycron
00 7 * * * echo hi mother, i wanna be a script daddy.
:wq
crontab mycron
how... (4 Replies)
Discussion started by: alikun
4 Replies
3. HP-UX
Hi all,
i want a job to run first monday of every of month. (1 Reply)
Discussion started by: megh
1 Replies
4. UNIX for Dummies Questions & Answers
Below are two cron entries. what is the difference beteeen writing 20 and */20? how is "20 * * * *" different from "*/20 * * * *"?
1) 20 * * * * find /tmp/ -name "*.log.*" ! -name "*.gz" -mmin +1440 -exec gzip '{}' \;
2) */20 * * * * find /tmp/ -name "*.tmp.*" ! -name "*.gz" -mmin +1440... (6 Replies)
Discussion started by: niks
6 Replies
5. UNIX for Advanced & Expert Users
Is there a way in AIX to schedule a script to run bi-weekly through cron?
I have a script that needs to run every other Wednesday, and this is what I thought I had to enter in the crontab file:
00 08 * * 3/2 /home/user/user.script
It didn't like that. It reports a syntax error. I'm almost... (5 Replies)
Discussion started by: LPT
5 Replies
6. 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
7. UNIX for Dummies Questions & Answers
How do I start, restart and stop the cron service under Slackware 12? (1 Reply)
Discussion started by: proactiveaditya
1 Replies
8. Shell Programming and Scripting
Hi All,
I have a script which is scheduled in the Cron. It runs every 10th and 40th min of an hour.The job has to run every 30min.
But, I do not want to have the 00:10 MST run every day.Is it possible to exclude that run from the schedule?Or any other way through which i can run my job every... (4 Replies)
Discussion started by: sparks
4 Replies
9. UNIX for Dummies Questions & Answers
I have a script that backs up a directory, creates a log file and mails the log file to us.
find . -print | backup -ivqf/dev/rmt0 | tee backup.log
cat backup.log|mail -v -s "Tape backup log" maillist
This script works fine from the console.
When I schedule it in cron, I never get the... (1 Reply)
Discussion started by: landog
1 Replies
10. Red Hat
Hi Everybody,
I want to run a script at every 5 seconds. I know how to run it every 5 minutes, is there any possibility to run a script at 5 seconds interval.
Regards,
Mastan (3 Replies)
Discussion started by: mastansaheb
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)