10-02-2008
This is a difficult problem ..
Well, it has been a few days since I posted this thread. So far are there are 36 viewers and 0 replies
![Frown Smilie](https://www.unix.com/images/smilies/frown.gif)
This must be a challenging one.
While waiting for a solution, I've found a "not so clean" way to delete a specific task in the crontab queue.
crontab -l > filename_list
sed -e '/file/d' filename_list > filename_queue
crontab filename_queue
The above 3 codes: First, get the queue list. Second, remove a specific line or lines from this list. Third, put the list back into queue.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
My cronjob triggers the script late by 6 minutes.
/var/cron/log shows that it got triggered at the right time then where can I track, the late starting of the script.
Is there some queue mechanism, some log?
This happens sometimes, not daily. but it affects me, whenever it happens.
Logging... (1 Reply)
Discussion started by: pksingh2
1 Replies
2. AIX
Hi every1
Well i have a list of numbers e.g
12304
13450
01234
00123
14567
what i want is a command to check if the number is starting from 0 and then delete the 0 without doing anything else!!!!
any help wud b appreciated!!!!!!!!:( (4 Replies)
Discussion started by: masquerer
4 Replies
3. Shell Programming and Scripting
I have a file contains
TASK gsnmpproxy {
CommandLine = $SMCHOME/bin/gsnmpProxy.exe
}
TASK gsnmpdbgui {
CommandLine = $SMCHOME/bin/gsnmpdbgui.exe
I would like to comment and than uncomment specific task eg TASK gsnmpproxy
Pls suggest how to do in shell script (9 Replies)
Discussion started by: madhusmita
9 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I have these files in my directory.
ABC123 ABC12.sls.20080809111121
ABC233 ABC12.sls.20080403123212
ABC543 ABC12.sls.20080804231212
ABC323 ABC12.sls.20080809111232
ABC765 ABC12.sls.20080809112343
ABC654 ABC12.sls.20080809113133
I want to delete only files in first... (2 Replies)
Discussion started by: i.scientist
2 Replies
5. Shell Programming and Scripting
I have an task definition listing xml file that contains a list of tasks such as
<TASKLIST
<TASK definition="Completion date" id="Taskname1" Some other
<CODE name="Code12"
<Parameter pname="Dog" input="5.6" units="feet" etc /Parameter>
<Parameter... (3 Replies)
Discussion started by: MissI
3 Replies
6. Shell Programming and Scripting
Hi,
I am currently writing a shell script to enter daily reoccurring jobs into the crontab. I want to be able to specify any two dates for which I want these daily jobs to run between.
Below is an example of what I need to be written to crontab.
# Give a start day of 21/10/2009 09:00... (2 Replies)
Discussion started by: JM_86
2 Replies
7. Shell Programming and Scripting
Hello all.
I need some help modifying the following script:
#!/bin/bash
#PBS -l nodes=1:ppn=8,walltime=48:00:00,os=centos53computeA
## To submit type: qsub x.sh
# If not an interactive job (i.e. -I), then cd into the directory where
# I typed qsub.
if ; then
if ; then
cd... (3 Replies)
Discussion started by: marcozd
3 Replies
8. Shell Programming and Scripting
Hio, So I have a crontab delete of older files setup. This script works fine if I run them by each individual directory.
Problem is there are so many thousands of files and hundreds of directories and sub directories that I need to recursively have it go through and delete files by directory... (2 Replies)
Discussion started by: vsekvsek
2 Replies
9. Shell Programming and Scripting
I am trying to run a script from crontab but the entire script (which is 70+ lines) is written in bash and I need it to run from a certain directory.
So when I run it manually I cd to /local/mnt/scr and then type ./reordersc and it works fine.
However, I want it to run from the crontab and I... (20 Replies)
Discussion started by: newbie2010
20 Replies
10. Shell Programming and Scripting
I will appreciate if you help me here in this script in Solaris Enviroment.
Scenario:
i have 2 files :
1) /tmp/TRANSACTIONS_DAILY_20180730.txt:
201807300000000004
201807300000000005
201807300000000006
201807300000000007
201807300000000008
2)... (10 Replies)
Discussion started by: teokon90
10 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)