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 OPENDARWIN
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.10 1 Mar 1994 queuedefs(4)