I have the following crontab entry.
0,30 00-16 * * *
This job runs every 30 minutes between the hours of 12:00AM and 4:00PM. How can I have it stop at 4:30PM instead?
Thank you,
David (3 Replies)
i have set the below one in cronta, expecting that it would run every fourth saturday for Jan, Apr, Jul and Oct,
but it comes out that it run everyday between 21 to 27.
Please help!!
00 01 21-27 1,4,7,10 6 my_job (1 Reply)
I have a script which shoud run after every 30 minutes.Though I know abt crontab, unfortunately I dont have access/authorization to use crontab in my terminal.
Could any one pls let me know how to schedule the script without crontab ?
Regards
Prashant:) (3 Replies)
Hi,
I have a script which will query the DB and added to crontab at 1,2,6,7 AM everyday and sends a email if count is 0.
Now the problem is, if crontab is disabled it doesn't sends a mail.
Please tell me how can I handle this situation in the script. (2 Replies)
All,
I'm a newbie with crontab and I need your help with schedule a cold-backup running every Sunday at 7am except 1st of the month.
Thank you so much. (2 Replies)
Hi,
My script is in $home/bin/sample.sh.
I want to run the script for 3times a day,
first execution will be at 08:00 am.
second execution will be at 16:00 pm
third will be at 23:59 pm.
what will be the entry with this requirement?? (1 Reply)
Hello all, I am a complete newbie to Unix and therefor also to this forum. I have an assignment for Uni, and need your help to understand something.
I need to use crontab and tar to schedule a weekly backup of a folder and its contents. I want the tarball to be stored in the users/float... (6 Replies)
Hi All,
How to schedule crontab on all day except sunday and monday means from tuesday to saturday at 06:00AM. (3 Replies)
Discussion started by: Riverstone
3 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE queuedefs(4)