I have a script which goes out and installs a package on a box remotely and im trying to get it to add a cron job too..but im having a few problems, whilst it does add the entry it wont run unless I connect to the machine , crontab -e, then :wq. This re-reads the configuration file and it will now run. so i tried in my script the following methods
1) I tried to edit the cron file for root directly
But i realised that the process would need to be HUP'ed to re-read this conf file so i tried adding
I come in the next morning and I check /var/cron/log and nothing has run. However, as i said, if i crontab -e and then save it immediately (:wq) then it will work fine
2) Ok, as far as im aware the above should have worked but I thought id try another method, this according to my colleague would definately work. Output crontab -l to a temp file , append the line to the temp file and use crontab <filename>. to re-read it in...
Same thing, come in next morning nothings happened, log onto box crontab -e, then immediately same it (:wq) and all is working ..
Does anybody have any idea on how i can get this to work
I can see where the nohup command can come in very handy. My question is, do you have to do something like this (nohup) in order to run certain cron jobs? On the windows side, I have a couple of scripts that basically run continuously, so all I have to do is ctrl-alt-del to lock my workstation,... (2 Replies)
A co-worker is having trouble w/ a job scheduled from cron and I got involved. Unfortunately I couldn't seem to find the answer and need some help. First off, I'm pretty sure he's using redhat linux. Anyway, I want to schedule a cronjob to run a java class. Let's say that, logged in as root, I... (3 Replies)
I have a script that needs to install a script the runs just before cron starts. Currently (for 9 and older), it simply finds the name of the cron script in /etc/rc?.d, decrements the number and creates a link.
For example, if cron starts with /etc/rc2.d/S75cron, the install script extracts the... (3 Replies)
Folks;
I have this script in SUN which if i run it using command line, it works fine, but when i run it using cron, it work but it misses one thing. here's the details
#!/bin/bash
cd /opt/new_script
for i in ./report*Groups.sh; do $i $1; done
This script above when runs through cron, it... (4 Replies)
folks;
This might sounds stupid, but i tried few ways to solve it without luck.
I need to run a job on the first Saturday of every month at 10 pm. so far i'm not sure what am i doing wrong, but every time i set it, it always run every Saturday instead of the first Saturday of every month.
Any... (4 Replies)
with the cron format
* * * * *
| | | | | |
| | | | |
| | | | +---- Day of the Week (range: 1-7, 1 standing for Monday)
| | | +------ Month of the Year (range: 1-12)
| | +-------- Day of the Month (range: 1-31)
| +---------- Hour (range: 0-23)
+------------ Minute ... (1 Reply)
Hi,
We have developed the script which will send an (html)attachment in through mail. The stand alone script is working fine ,but when we schedule it cron the "nail" command is not working that is we are not receving any mail.
Following is the command which we used to send the mail. :confused:... (4 Replies)
Hi,
I have a cron job that I want to run twice a week, on Tues/Thurs, and I want it to run three times - specifically at 10pm, 11:10pm, and 12:20am respectively.
I "think" the way to do this is to run the following:
00,10,20 22,23,00 * * 2,4 MYCOMMAND
Just wanted to verify this... (4 Replies)
Discussion started by: xdawg
4 Replies
LEARN ABOUT POSIX
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)