Sponsored Content
Top Forums Shell Programming and Scripting Don't want to invoke job on holiday! Post 302100641 by reborg on Thursday 21st of December 2006 05:49:44 AM
Old 12-21-2006
I usually put such logic in the scripts, or in a wrapper script to do this.
 

6 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Happy Thanksgiving Holiday!

Happy Thanksgiving holiday, everyone! Let's leave the computer alone, forget the Unix/Linux for a while, and enjoy your turkey and Foot~~~~~~~~~~~~~~~~~~~~~~ball~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (1 Reply)
Discussion started by: HOUSCOUS
1 Replies

2. Shell Programming and Scripting

holiday

hey all, I have set up a cron job which would be invoked at 1:00 am everyday. However, there is really no need to invoke such job if it's a public holiday so I am wondering if anyone have any idea on how to approach this? Thanks in advance! (2 Replies)
Discussion started by: mpang_
2 Replies

3. What is on Your Mind?

Discussing Holiday Season Greetings with jlliagre

Hmm, didn't you press that "Submit new thread" button too early ? ;) Reference this post: https://www.unix.com/whats-your-mind/124692-seasons-greetings-happy-holidays-unix-linux-forums.html (15 Replies)
Discussion started by: jlliagre
15 Replies

4. UNIX for Dummies Questions & Answers

Run scripts through AutoSys depending on holiday

Hi all, I am new to autosys. Can anyone help me in writing autosys job for the below script? Requirement is : 1.Every day it should run this script at particular time except on holidays. 2.The day after holiday some other script should be running. Thanks in advance. #!/bin/ksh #set... (0 Replies)
Discussion started by: raghuramyenni
0 Replies

5. What is on Your Mind?

Are we having sat-sun holiday for unix forum?

Are we having sat-sun holiday for unix forum? I am just thinking there are no new things to explore on sat-sun. It looks like holiday for this site also....:D (1 Reply)
Discussion started by: pamu
1 Replies

6. What is on Your Mind?

Holiday Thoughts for the End of 2018

Happy Holidays. Here are my randoms thought at the end of 2018 in no particular order. You Are Truly Blessed IT people are lucky. We get to use our brains extensively to solve complex and challenging computer-technology related problems. This is very good for our brains. Programming,... (2 Replies)
Discussion started by: Neo
2 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 12:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy