10-24-2009
What we need to see is what happened around the time that the jobs should have executed and didn't. I suggests that you set up a crontab. When it fails, post the part of the log that covers 1 hour before the failure time to the end of the file.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have a script which I am able to run from command line. When I put this in cron, it fails and gives the following message:
ld.so.1: /d00/documentum/product/5.2.5/bin/dmbasic: fatal: libdmcl40.so: open failed: No such file or directory
The ksh script looks like this:
# Set this... (1 Reply)
Discussion started by: nattynatty
1 Replies
2. Shell Programming and Scripting
Hi ,
I have an issue with cron job that i have scheduled today. The problem is that when i run this script in command prompt it work good giving me the desired results but if i schedule this to run using cron job it failes giving a "syntax error in line 11 :$"..... Can anyone look into this and... (6 Replies)
Discussion started by: bsandeep_80
6 Replies
3. Solaris
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Discussion started by: ron76
3 Replies
4. UNIX for Dummies Questions & Answers
This is regarding my cron job. My cron entry
30 * * * 1-5,0 /work1/informix/sample/script1.sh
31 * * * 1-5,0 /work1/informix/sample/script2.sh
Every 30 mins script1.sh is run. (mon thru friday and sunday)
Every 30 mins script2.sh is run. (mon thru friday and sunday)
This is based on the... (3 Replies)
Discussion started by: kenkanya
3 Replies
5. Shell Programming and Scripting
Hi ,
I want to run script every minute so i added .
cron entry as below usning crontab -e
looks like
*/1 * * * * sh /home/sai/http_sim/http_start.sh
but cron job is not running ?
any way to start the cron or something ?
Thanks,
Raghavendra (2 Replies)
Discussion started by: raghavendra.nsn
2 Replies
6. Shell Programming and Scripting
I want to update svn code using a nightly job using cron, i have created a job in cron as,
30 17-19 * * 1-5 /home/saprab/svnUpdate.sh <branch> <svnusername> <svnpassword> >> <logfile> 2>&1
svnUpdate.sh :
===============
#!/bin/bash
branch=$1
svnuser=$2
svnpass=$3
cd ${branch}... (2 Replies)
Discussion started by: bhavesh.sapra
2 Replies
7. Shell Programming and Scripting
Hi
I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies
8. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
9. UNIX for Beginners Questions & Answers
Dear Members
Seeking you help on my issue.
this script need to run on every end of month.i configured as below.
but it runs everyday.
why
0 9 28-31 * * ] && /usr/bin/bash /u01///scripts/e.sh (3 Replies)
Discussion started by: ded325
3 Replies
10. UNIX for Beginners Questions & Answers
My Friends
I want to run a script only at the end of month.but i tried below cront entry its not working. pls help
0 9 28-31 ] && /usr/bin/bash /u01/app/scripts/CX-eom.shOs Details: AIX 7.1.0.0
Please use CODE tags as required by forum rules! (5 Replies)
Discussion started by: ded325
5 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)