10-24-2009
hi JP
from big intervals i mean, like wen i change the schedule with just minutes, it do work, but if the next schedule is after few hours, as i mentioned in my crontab example, it do not run the script
And, m sorry m new to Cron as well as Linux, and m not sure how to set the rest of the attirbutes, and wat exactly do they require for..
and if these attributes do effect, then i believe the cron job shud not work for the rest of jobs as well, that i run if i change the same to minutes.
thanks
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have a script which I am able to run from command line. When I put this in cron, it fails and gives the following message:
ld.so.1: /d00/documentum/product/5.2.5/bin/dmbasic: fatal: libdmcl40.so: open failed: No such file or directory
The ksh script looks like this:
# Set this... (1 Reply)
Discussion started by: nattynatty
1 Replies
2. Shell Programming and Scripting
Hi ,
I have an issue with cron job that i have scheduled today. The problem is that when i run this script in command prompt it work good giving me the desired results but if i schedule this to run using cron job it failes giving a "syntax error in line 11 :$"..... Can anyone look into this and... (6 Replies)
Discussion started by: bsandeep_80
6 Replies
3. Solaris
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Discussion started by: ron76
3 Replies
4. UNIX for Dummies Questions & Answers
This is regarding my cron job. My cron entry
30 * * * 1-5,0 /work1/informix/sample/script1.sh
31 * * * 1-5,0 /work1/informix/sample/script2.sh
Every 30 mins script1.sh is run. (mon thru friday and sunday)
Every 30 mins script2.sh is run. (mon thru friday and sunday)
This is based on the... (3 Replies)
Discussion started by: kenkanya
3 Replies
5. Shell Programming and Scripting
Hi ,
I want to run script every minute so i added .
cron entry as below usning crontab -e
looks like
*/1 * * * * sh /home/sai/http_sim/http_start.sh
but cron job is not running ?
any way to start the cron or something ?
Thanks,
Raghavendra (2 Replies)
Discussion started by: raghavendra.nsn
2 Replies
6. Shell Programming and Scripting
I want to update svn code using a nightly job using cron, i have created a job in cron as,
30 17-19 * * 1-5 /home/saprab/svnUpdate.sh <branch> <svnusername> <svnpassword> >> <logfile> 2>&1
svnUpdate.sh :
===============
#!/bin/bash
branch=$1
svnuser=$2
svnpass=$3
cd ${branch}... (2 Replies)
Discussion started by: bhavesh.sapra
2 Replies
7. Shell Programming and Scripting
Hi
I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies
8. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
9. UNIX for Beginners Questions & Answers
Dear Members
Seeking you help on my issue.
this script need to run on every end of month.i configured as below.
but it runs everyday.
why
0 9 28-31 * * ] && /usr/bin/bash /u01///scripts/e.sh (3 Replies)
Discussion started by: ded325
3 Replies
10. UNIX for Beginners Questions & Answers
My Friends
I want to run a script only at the end of month.but i tried below cront entry its not working. pls help
0 9 28-31 ] && /usr/bin/bash /u01/app/scripts/CX-eom.shOs Details: AIX 7.1.0.0
Please use CODE tags as required by forum rules! (5 Replies)
Discussion started by: ded325
5 Replies
LEARN ABOUT SUNOS
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)