1) do what you expect from cron: write logs. The cron log logs the cron activity, not the activity of the processes started by it. Put some logging messages into your script and write your own log to find out where it goes wrong, like this:
Then analyze the content of $logfile and find out where it went off track, hence reducing the scope of your analysis. rearrange the log messages to monitor more closely the part where it went wrong, etc., etc....
2) Take the measure Nr 1 for all problems of the i-have-written-a-script-and-it-works-but-i-put-it-in-cron-and-it-failed-type: set that damn environment because cron won't do it for you!
Hi,
I want to run my shrip for every 30 min..
if i enter crontab -l i am getting following..
00,10,20,30,40,50 * * * * /home/arbuser/temp2/perform/per.sh
00,15,40,35,50 * * * * sh home/arbuser/temp2/perform/per.sh
if I enter like this :
ps -ef |grep cron
root 311454 1 0... (3 Replies)
I am having a problem running a shell within CRON. It will run successfully if I do not inject a .profile into the entry. However, the second I place a . profile in front of the shell, the job does not execute. Any ideas? (4 Replies)
The cron daemon on one of my HP boxes is giving the following error:
I checked the queuedefs man page, and it has left me a bit confused. The man page says:
So this means that no more than 100 cronjobs can be run at one time (we do not use at and batch on this system).
The... (4 Replies)
Hi,
I've just done a school boy error.
I was trying to edit the crontab but instead of using:
crontab -e
I used crontab -r without realising. Then went to look at the crontab but ntohing their. Looked int he manual and -r removed the crontab.
Is their any way of getting this back??
... (3 Replies)
Hi frnds...
I m facing very irritating problem already waisted my 2 days..
I have a following script..( i am pasting only the main code)
ftp -ivn 213.194.40.77 <<FTP
user $user $password
binary
cd $FileDir/out
lcd $localpath
get $file
rename $FileDir/out/$file $FileDir/tmp/$file... (7 Replies)
I'm using Red Hat and I need to get cron working and I'm not sure what the problem is. As a test I've done the following:
1) In /etc/cron.d I've created a file called date with the following contents
2) */1 * * * * root date >> /root/thedate
3) This works perfectly. It sends the date every... (1 Reply)
Hello folks,
I've got a few cron jobs listed under a particular user id. They are running fine but then they are creating a new process every time they are running. Any idea folks? (3 Replies)
Hi i am new here and have a quick question.
i am receiving ./project.sh: line 12: syntax error near unexpected token `newline'
./project.sh: line 12: `echo "`date +"%F %R"` `md5sum /etc/passwd`" >> '
error message
here is my script. could you please help!
#!/bin/bash
# PROGRAM:... (4 Replies)
Just wanted to know, what happens if a user exists in both files cron.allow and cron.deny.
Will the user be able to set cron?
Thanks,
Deepak (7 Replies)
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
LEARN ABOUT SUNOS
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)