Hi All,
I want to run a cron job to run on the first saturday of each month at 1:30am. Would the following entry suffice this condition
30 1 6 * 6 wall %Will this work%
Appreciate your time. (1 Reply)
Hi,
Where can we find Cron job logs?i have a cron job which is not executing at all,
00 12 * * * /xx/yy/job > /pp/qq/log
if i execute the job alone,it is executing fine.
>/xx/yy/job > /pp/qq/log (is executing fine)
but its not executing when it triggered from cron.is there any place cron... (7 Replies)
Hi folks,
I have got the following cron entry ...
08 30 * * * /mp1/scripts/test.sh > /mp1/scripts/test_logs.txt 2>&1
The problem is that instead of generating a new test_logs.txt file every time it keeps on appending the outputs to the test_logs.txt file. What is it that I am doing wrong... (2 Replies)
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
Hi,
I need some clarification on cron entries. I have a cron job like..
15 01 19 02 6 exec /usr/bin/test.ksh
and I have another cron entry added, which is
15 01 20 02 6 exec /usr/bin/test.ksh
So, I am thinking the second cron entry shouldn't have run because 02/20 is Sunday, but... (1 Reply)
I am trying to get the string containing date - in a specfic format actually, although I think that part is inconsequencial - 1110226^1110226^1110226^1110226^1110226 - through echo or printf or in some other way - created within a cront job and passed as a parameter to a perl script.
Now, I know... (3 Replies)
Hi,
I have to add two cron entry now. Please correct me if anything wrong
Below script should run at every one and half hour.
30 01 * * * /export/home/gxadm/scripts/collect_mq_info.pl $HOME/GCSS/logs > /dev/null 2>&1
Below script should run at every 2 hours
0 02 * * *... (9 Replies)
In my cron thare is a line like
24 11 * * * /usr/batch/bin/abc.sh > /usr/batch/log/abc.log 2>&1
along with other entries. I want to comment out this line through a shell script. My local variable 'line'ontains the full entry (i.e. 24 11 * * * /usr/batch/bin/abc.sh > /usr/batch/log/abc.log... (4 Replies)
My first post evidently did not materialize so I posted it again:
Runnning a cron job every 5 mins to send data files to a state facility.
My original cron entry at worked fine:
01,06,11,16,21,26,31,36,41,46,51,56 * * * * /home/sftpuser/stateinoc-from-appname.ksh
Somewhere I have a... (1 Reply)
Hi
I have a system running solaris 11, in which I am able to execute a script from the command line, but once I put i the crontab does run, but do not give results.
The entry is:
15 11 * * * /var/oswbb/./startOSWbb.sh >> myjob.log 2>&1
30 11 * * * /var/oswbb/./stopOSWbb.sh
I have check... (2 Replies)
Discussion started by: fretagi
2 Replies
LEARN ABOUT SUSE
cron
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)