11-28-2013
It all depends on how you modified the crontab. Did you use the proper tools or did you edit it directly?
Let's not talk about your specific problem for a moment and just say a few things about the cron daemon in generic Unix terms.
***
The cron daemon starts at boot time and loads all the user crontabs into memory. It makes a note of the last modified date/time of each table.
Periodically the daemon will wake up and go and check the user crontabs on disk to see if any of them have changed (by checking again the date/time modified). If it finds that it doesn't have the latest copy of a crontab in memory, it will reload that table and any new cron jobs will be scheduled. Until that time the new jobs will not be run.
So if you were to modify a crontab directly scheduling a job to run one hour later then don't expect it to work.
The workaround would be to stop and restart the cron daemon (see cron man page) but you would need to be root to do that.
***
Perhaps you just need to wait up to 24 hours to see if it begins to run your new cron job.
If you use the proper tools to insert a new cron job then cron knows that you've done it and the job will schedule immediately.
Hope that helps.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
i have a scripts that update an SQL DATABASE using sqlplus command.
when i run it in a interactive mode its ok but when try to run it using the crontab i get an a messege :
"Must be attached to terminal for 'am I' option"
(there is no "who am i" command in the script)
and the DB... (4 Replies)
Discussion started by: dorilevy
4 Replies
2. Shell Programming and Scripting
Like class loader in java, can we make a function loader in shell script, for this can someone throw some light on how internally bash runs a shell script , what happenes in runtime ...
thanks in advance.. (1 Reply)
Discussion started by: mpsc_sela
1 Replies
3. UNIX for Advanced & Expert Users
Hi experts,
need your helpo.
after editing the crontab while saving the file it says-
"/tmp/crontabRlaauT" 1 line, 77 characters
cron may not be running - call your system administrator
And i checked after certain time. script in cron is not running. I got a mail in user saying... (1 Reply)
Discussion started by: thepurple
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
down here part of the scheduled job in crontab (AIX Version 5)
i have problem running jspPRE-ALL.
i verrify permissions and privileges (the others job are working good)
if i run the job in command line it work correctly
#
# Aggiornamento doni e continuity
00 02 * * 2-6... (5 Replies)
Discussion started by: ilpasta
5 Replies
5. Shell Programming and Scripting
Hi, I posted this in the Solaris forum but I think this one would be more appropriate.
I created a script starting with the following lines:
#!/usr/bin/ksh
flag=n
export flag
typeset -i quant=0
(...)
When running it I'm getting the following 2 errors:
/tmp/tstscript/testfail.ksh:... (9 Replies)
Discussion started by: Cvg
9 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
Here is my command which I've scheduled to be run from crontab, but it's giving error message: rah: rahhost executable needed but not in PATH
My cmd is-
36 10 * * * /opt/IBM/dwe/db2/V9.5/bin/rah "df -m" >> /db2home/bculinux/Files/log/db.out 2>&1
Though I've added path... (5 Replies)
Discussion started by: NARESH1302
5 Replies
7. UNIX for Advanced & Expert Users
Hi,
I have created the below script,
set -x
# Set the Path of Environment file
ENV_FILE_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/bin
LOG_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/log
export ENV_FILE_DIR
export LOG_DIR
# Set Audit Environment
. ${ENV_FILE_DIR}/QDM.env... (8 Replies)
Discussion started by: yohasini
8 Replies
8. Solaris
I have set up my cron job on the solaris SunOS 5.10 Generic_138888-03 sun4u sparc SUNW,UltraAX-i2 but it is not running on time as expected.
Would you please help me to find out what I did wrong?
I want to have this cron job run once every month on the 1st Wednesday of the month, but it ran... (6 Replies)
Discussion started by: ggcc
6 Replies
9. UNIX for Dummies Questions & Answers
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
Discussion started by: abhi_123
7 Replies
10. Shell Programming and Scripting
Hi experts,
Need your help to schedule the script(test.sh) bi-weekly in linux machine.
script need to run at every alernate thursday at 9 am .
Please help to run the same. (6 Replies)
Discussion started by: abhigrkist
6 Replies
LEARN ABOUT OPENSOLARIS
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.11 1 Mar 1994 queuedefs(4)