Since you did not specify the OS, please pay attention to a few things about cron:
Some OS will send messages (yes error messages...) if the standard output and STD-err are not specified ( redirected to files...)
the same goes if you have in your envirronment things related to interactive shell (e.g TERM set etc...)
be aware also the PATH is VERY limited and no user env. bariable are set...
(That is the first thing that should come to your mind if a job fails when using cron but works when you execute it by command line...)
Last edited by vbe; 06-05-2012 at 11:11 AM..
Reason: typos
hi all
how to schedule a cron job running on last day of every third month at
12 midnight
will the following work
0 0 30,31 3,6,9,12 * <required file>
thanks (3 Replies)
Sometimes cron really upsets me and I cant figure out these types of wierd dates, but how do I get cron to run something on every other sunday? I am running Solaris 8.
-S (4 Replies)
Hi Everyone , have a nice day
given below is the line i have added in crontab
* * * * * /Rauf/script2.sh
intended to run this script after every minute , when i run this script manually it runs fine and produces output , but after adding it to crontab ( like given above ) , it doesnt work
... (5 Replies)
Hi,
i need to setup a cronjob that has will execute iostat command from morning to evening time.
for instance the timing has will be like this.
8:00 A.M -- 6:00P.M
how to define this entry in crontab
Regards (3 Replies)
hi
i am new in solaris. i am accessing server through putty. i could not add entry in crontab.
i have given "crontab -e" for add a new entry. It is not coming. what parameter i have to set for getting crontab -e
thanks (1 Reply)
Discussion started by: sunnybee
1 Replies
LEARN ABOUT OSF1
cron
cron(8) System Manager's Manual cron(8)NAME
cron - The system clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
The cron daemon runs shell commands at specified dates and times. Commands that are to run according to a regular or periodic schedule are
found within the crontab files. Commands that are to run once only are found within the at files. You submit crontab and at file entries
by using the crontab and at commands. Because the cron process exits only when killed or when the system stops, only one cron daemon
should exist on the system at any given time. Normally, you start the cron daemon from within a run command file.
During process initialization and when cron detects a change, it examines the crontab and at files. This strategy reduces the overhead of
checking for new or changed files at regularly scheduled intervals. The cron command creates a log of its activities. The cron daemon
must be started from the system startup scripts because it must begin execution without a login user ID set. The cron daemon starts each
job with the following process attributes stored with the job by the invoking process: Login user ID Effective and real user IDs Effective
and real group IDs Supplementary groups
It also establishes the following attributes from the authentication profile of the account associated with the login user ID of the invok-
ing process: Audit control and disposition masks Kernel authorizations
DIAGNOSTICS
The at and batch programs will refuse to accept jobs submitted from processes whose login user ID is different from the real user ID.
FILES
Specifies the command path. Main cron directory Directory containing the crontab files. List of allowed users. List of denied users His-
tory information for cron Queue description file for at, batch, and cron
RELATED INFORMATION
Commands: at(1), crontab(1), rc0(8), rc2(8), rc3(8)
Files: queuedefs(4) delim off
cron(8)