04-07-2008
comment jobs in cron for multiple accounts
Hi,
We have several jobs scheduled in cron in AIX. Before every release
we need to comment those jobs and uncomment those after the release is over.
There are several accounts whose cron entries need to be commented.
Can anyone provide me with a script which can put a '#' before each line
in each account's cron entries. I may pass the accountname as parameter
or can keep in a file and read from there and loop through. I have root and
can run with that.
Thanks in advance.
This User Gave Thanks to shibajighosh For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I was wondering if itīs possible to cron job not to run on a certian day and time. Iīve got a job that runs everyday at 08:00
but would like it not to run on the 20:th between 08:00 and 10:00
Anyone know if this is possible, and if. How do i do it?
regards...
dOzY (3 Replies)
Discussion started by: dozy
3 Replies
2. Solaris
I'm trying to run cron jobs to start any inhibited processes after a system reboot.
I can schedule th cron, but i'm confused as to how to incorporated the reboot, since reboot is scheduled at different times, once every month.
How can I write this to start every 15 min after after a reboot
... (2 Replies)
Discussion started by: Remi
2 Replies
3. UNIX for Dummies Questions & Answers
Hello All,
Hopw all is fine. I am newbie to Unix. I am using Bourne Shell (sh). One of the question I have is that I am trying to read XML file and based on reading that XML file I want to run different java programs at different hours. Meaning
05 14 * * * java ./program1
10 14 * * * java... (3 Replies)
Discussion started by: samshaw
3 Replies
4. Shell Programming and Scripting
Greetings,
I am creating a ksh script to automate the installation of a utility on many servers.
As part of this install, I want to check for a job in root's crontab.
If the job exists, I need to comment it out.
I know I will need to copy off the crontab then read it back in, but I am... (4 Replies)
Discussion started by: 22blaze
4 Replies
5. Shell Programming and Scripting
Hi,
My requirement is to comment/uncomment a cron job through a script.
1. Redirected the output of crontab -l to a text file.
crontab -l >cronoutput.txt
2. grep to find the script running and sed to place the comment (#) as
the first char
grep -i 'weblogicmonitor.sh'... (5 Replies)
Discussion started by: mannepalli
5 Replies
6. UNIX for Dummies Questions & Answers
Hi
I want to view the schedules of all the crons under all accounts running on the UNIX server.
crontab -l list the crons under my account. How to view the cron schedule of other accounts? Does it require root access?
Is there a way to view the all the Crons scheduled on an UNIX server?
... (0 Replies)
Discussion started by: ashok.k
0 Replies
7. Solaris
There are two jobs in Solaris , Cron and at jobs..
I know how to disable or enable cron jobs.
How can I enable at jobs and disable it.
Kindly help.
Rj (2 Replies)
Discussion started by: jegaraman
2 Replies
8. Shell Programming and Scripting
Hi,
I ran two crontab commands
using:
crontab program1
crontab program2
However when I type crontab -l only the second cron job shows up, how do I see all cron jobs running and how do I edit all at the same time
Thanks in Advance
S:D (10 Replies)
Discussion started by: walforum
10 Replies
9. Shell Programming and Scripting
I have multiple jobs and each job dependent on other job.
Each Job generates a log and If job completed successfully log file end's with JOB ENDED SUCCESSFULLY message and if it failed then it will end with JOB ENDED with FAILURE.
I need an help how to start.
Attaching the JOB dependency... (3 Replies)
Discussion started by: santoshkumarkal
3 Replies
10. UNIX for Beginners Questions & Answers
I have two scripts which I'm tying to run one after the other- this is what I've tried:
00 14 * * * /path/one.sh && /path/two.sh
I've also tried putting each script on a different line:
00 14 * * * /path/one.sh
00 14 * * * /path/two.sh
Can this be done? (1 Reply)
Discussion started by: $shell_Learner
1 Replies
LEARN ABOUT PHP
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)