02-16-2009
See the cron log (usually /usr/adm/cron/log) to see whether the cron ran at all and if it failed with an exit code (rc=n).
Untrapped errors from root cron will be found in root mail.
You can only edit the root cron if you have root permissions.
The cron daemon will only notice the changes to a crontab if they were made with the appropriate "crontab" command or cron itself was restarted.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all
we r using hpUX11.00 9000 sever as oracle 8i db server...
But the problem is we have 4 instances of dbs but upto my knowledge there are only to ports available for TNS listen...
how can i configure or get wht ever it may be the other two ports for tns listener.........
... (2 Replies)
Discussion started by: Prafulla
2 Replies
2. Shell Programming and Scripting
this is my lex file ------------ test.l
%%
printf("%c",yytext+'a'-'A');.ECHO;
how do i compile it
$ lex test.l cc lex.yy.c -o test -ll <------|
|
if this is correct do i add this line--------| @the command line or does it... (0 Replies)
Discussion started by: sinner
0 Replies
3. UNIX for Dummies Questions & Answers
need help....just wanna copy all files with no extensions but with tree-informations to one dir
first I make a new directory with all foldertrees...like
find / -name "*" -type d >a1
sed -e 's/^/new/g' <a1 >b1
mkdir -p `cat a1`
then I wanna copy all specific files with no... (12 Replies)
Discussion started by: svennie
12 Replies
4. Solaris
Server 1 SSH Version Sun_SSH_1.0
Server 2 OpenSSH_3.8.1p1
Server 3 OpenSSH_3.8p1
I created the rsa keys on server1. Public and private. I copied the id_rsa.pub file to server2 and server3 and appended this to the authorized_keys file in the .ssh directory on both. (All servers using the root... (2 Replies)
Discussion started by: frustrated1
2 Replies
5. Shell Programming and Scripting
I do not have the luxery of a server that i can try on, so i had to post my qn here.
Say i have two jobs in the cron table, the jobs are scheduled 2 mins apart. Assuming the first jobs does a lot of operations and takes > 2 mins. Will the second job be executed? Will Unix actually have a queue... (3 Replies)
Discussion started by: new2ss
3 Replies
6. Shell Programming and Scripting
Hi
I have written a shell script(in Solaris) in which following logic is there.....
i=1
while read control
do
key=`echo $control | awk -F$DELIMITOR '{ print $1 }'`
echo "Key Values" ${key}
i=`/usr/bin/expr $i + 1`
done < $CONFPATH/$CONFFILE
when i execute it at prompt it... (4 Replies)
Discussion started by: Amardeep
4 Replies
7. UNIX for Advanced & Expert Users
Hi,
if I launche this at commande line It is OK :
$ /home/oracle/anaschxt_A01_5_15_25_plemae.sh
but if I put it in crontab :
Like this :
I have this error :
/home/oracle/anaschxt_A01_5_15_25_plemae.sh: sqlplus: not find.
The script is :
+17 ... (2 Replies)
Discussion started by: big123456
2 Replies
8. UNIX for Dummies Questions & Answers
hi guys...
i m using rm *.zip or rm -rf *.zip while removing from a server path recursively,
i m getting "Remove directory operation failed."
if i use rm* .zip
i m getting as invalid command and none of the files are removed..
please help where m i wrong
when i execute the... (13 Replies)
Discussion started by: madhu_aqua14
13 Replies
9. Shell Programming and Scripting
Hi,
I have written a script for file scan :
#!/bin/sh
find . -name "common.log.diff" > /dev/null 2>&1
if ; then
cp common.log common.log.diff
diff common.log common.log.diff > DIFFERENCE.log
cp common.log common.log.diff
grep "ERROR" DIFFERENCE.log
if ; then
echo "1" >... (6 Replies)
Discussion started by: himvat
6 Replies
10. Debian
Hi all
I installed Debian and i have a few scripts that outputs what is happening.
The wierd part...after fresh install all works ok but after i open or edit Crontab it stops executing the scripts...and scripts runs manually so its not a problem with scripts...what happens is that i usually... (3 Replies)
Discussion started by: ro0t3d
3 Replies
LEARN ABOUT OPENDARWIN
cron
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)