Sponsored Content
Full Discussion: Schedule a job using Crontab
Top Forums Shell Programming and Scripting Schedule a job using Crontab Post 302404009 by fpmurphy on Monday 15th of March 2010 09:45:46 AM
Old 03-15-2010
If you can change 17.30 to either 17.00 or 18.00 you can do it with a simple cron entry, e.g.
Code:
00 17,23 * * * /path/to/job

Otherwise, one way would be to schedule the job for every 30 minutes between 17.00 and 23.00 and test for the two required times within your job.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to schedule a job

Hi, How can i schedule a job, i.e a program named p found at path a/b/c, to run at a time T everyday? Thanks (5 Replies)
Discussion started by: ashvik
5 Replies

2. UNIX for Dummies Questions & Answers

Crontab schedule

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)
Discussion started by: dkranes
3 Replies

3. Shell Programming and Scripting

Crontab schedule

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)
Discussion started by: sandy1028
2 Replies

4. AIX

Schedule Job

how to schedule a job in aix, pls explain with cmd (1 Reply)
Discussion started by: udtyuvaraj
1 Replies

5. UNIX for Advanced & Expert Users

Schedule a Crontab

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)
Discussion started by: hanie123
2 Replies

6. Shell Programming and Scripting

schedule job

Hi, I have a spcific box called abc in autosys and below that there are 2 jobs. my requirement is to run the abc box only on monday and rest of the day the rest of the jobs should be in success status.. ---------- Post updated at 03:11 PM ---------- Previous update was at 02:45 PM ----------... (4 Replies)
Discussion started by: j_panky
4 Replies

7. AIX

job run before schedule on crontab

Guys, yesterday i just make a script with email as a result and put them into crontab, it will execute on 23.33. Today, i recieved email from system twice as result the script. the first email send at 23.02 and the second send at 23.33 how is the script execute two times ? the first job run... (6 Replies)
Discussion started by: michlix
6 Replies

8. Shell Programming and Scripting

Crontab schedule

Hi all, I would like to schedule a crontab script, which should run From 8pm Thursday to 2am Friday and it should run every 10 minutes. I have put a script like below, is it the correct one. 10 01,02,20,21,22,23,00 * * 4-5 /u01/app/test.ksh Any other options available to schedule the same... (6 Replies)
Discussion started by: sid2013
6 Replies

9. Shell Programming and Scripting

Schedule Job Fortnightly (FRI) in Crontab

Solaris platform. How can I schedule crontab job every 2 weeks and the job to be scheduled on Fri? (7 Replies)
Discussion started by: KhawHL
7 Replies

10. Shell Programming and Scripting

How to schedule crontab?

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
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)
All times are GMT -4. The time now is 07:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy