01-26-2007
Quote:
Originally Posted by rujus
the log which has given in job scheduled is throwing 0 bytes file.but when it runs manaully the log is updating appropraite.
This kinda proves the assumption in my previous post is correct.
Directly at the start, the file is created since you redirect standard out.
But the cron job never reaches the point where it starts to produce data cause it failed on a command which it could not locate.
10 More Discussions You Might Find Interesting
1. AIX
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)
Discussion started by: rramanuj
1 Replies
2. Shell Programming and Scripting
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)
Discussion started by: King Nothing
2 Replies
3. Shell Programming and Scripting
Hi,
I am new to unix.
I have once made an entry into cron file for one scirpt to run. The script sends me email. But i want the script entry removed from the cron file.
But i am not able to find the entry in cron file. When i do crontab -e it shows content of the file but my script is... (3 Replies)
Discussion started by: ajincoep
3 Replies
4. Solaris
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)
Discussion started by: ksvaisakh
5 Replies
5. UNIX for Dummies Questions & Answers
Can someone please quickly respond to this?
I need to have a script test.sh to run every 30 minutes from Monday to Saturday from 6am to 10pm as a crontab entry...
Thanks. (3 Replies)
Discussion started by: everurs789
3 Replies
6. UNIX for Advanced & Expert Users
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)
Discussion started by: everurs789
1 Replies
7. Solaris
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)
Discussion started by: Mani_apr08
9 Replies
8. Shell Programming and Scripting
Hi All,
i have a folder in a server say xxx.xx.xx.xx\abcd\efgh. i want to make a cron job entry so that i would get a mail (me@example.com) on business days. will this help me...
30 4 * * 1-5 cd \abcd\efgh|ls-ltr|mailx:me@example.comhttps://www.unix.com/images/editor/code.png (10 Replies)
Discussion started by: mahesh300182
10 Replies
9. Solaris
Hi
I have one entry in my crontab that do not run, in cron, but it runs manually:
53 7 * * * /moneta_polled01/download/./get_dealer.sh
55 7 * * * /moneta_polled01/download/./mov_dealer.sh
The first entry do not run automatically, but it runs manually.
The second entry runs... (12 Replies)
Discussion started by: fretagi
12 Replies
10. Solaris
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
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)