06-21-2013
With standard versions of crontab, you can't do it in one line. (You could do 12:15 and 21:15 in a single line; but not 12:30 and 21:00.) Some implementations of crontab may accept time specifications that are extensions to the requirements of the standards. Use man crontab on your system to see if your implementation's version of crontab provides an extension that might do what you want.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I would like to schedule a command at a specific time on my system.I know that theres a file named at.alow and at.deny in my system. I can find the at.deny file but not an at.allow file .
Is there anyway out or i have to go and talk to the system administrator itself , or any other way of... (1 Reply)
Discussion started by: prashantuc
1 Replies
2. UNIX for Dummies Questions & Answers
i have tried to schedule my process at a certain time using the at command :
the error says bad time specification
can somebody help me
i used at 2300 job
thanks (2 Replies)
Discussion started by: prashantuc
2 Replies
3. Shell Programming and Scripting
Hi,
I need to write script which will read a value from XML file and schedule crontab accordingly.
I have an XML file which has a key value structure where the entries is:
<Param Name="executionInterval" Value="600" />
600 means that the crontab should be scheduled to run every 600 sec.
... (0 Replies)
Discussion started by: michaelbz
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
How can we run/schedule a shell script. Since there is no access to cron at this point of time we have to think other way out to run a script every hour.
How can we achieve this. Need advice.
How about using sleep,autosys etc...the script should trigger off every hour...which sends... (3 Replies)
Discussion started by: noorm
3 Replies
5. Linux
Hi Everybody,
How to schedule a job using cron that shouldn't run between working hrs 9am-5pm, while run in non working hrs every hour, every day of the month, month & week.
I tried the following way, not sure I can use logical not operator(!). Please correct me if wrong or suggest other... (2 Replies)
Discussion started by: sudhirav
2 Replies
6. Shell Programming and Scripting
Hi all,
My OS is Solaris 10. I want to schedule a job which i need to run between morining 6 to eve 6 once for every 2 hours. This is what i did.
0 6-18 * * 1-5 /monitor.sh
It runs for every hour how to make it for every two hours ......
Thanks,
Firestar. (1 Reply)
Discussion started by: firestar
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I need to schedule a script in crontab which should run at 01:00 am in the morning and should run for every 15 days in a month.
How to schedule this by using crontab?
Many thanks.
Rgds, (13 Replies)
Discussion started by: venkatesht
13 Replies
8. Shell Programming and Scripting
Hi,
i have 10 sh scripts. All are running in parallel using cron tab and each script gives "success" flag files once the execution is completed.
and, now i have 11th script which should look for "success" flag from those 10 sh scripts. once all the 10 flag files found, 11 th script has to do... (9 Replies)
Discussion started by: nago123
9 Replies
9. UNIX for Dummies Questions & Answers
Hi,
We can schedule a new job using crontab -e.
is there any other way to achieve the same(opening the file directly and add an entry).
I have tried to access /var/spool/crontabs directory. But i am getting permission denied error,
Please help me. Thanks (8 Replies)
Discussion started by: pandeesh
8 Replies
10. Shell Programming and Scripting
Hi All,
I am new to unix and i have a task in front of me.
The code part is "android update sdk" . I need to crontab this process.
Hence i have written a script that runs the above command and sends a mail once the update is done. The problem with the automation is the installer asks for a... (5 Replies)
Discussion started by: Kashyap
5 Replies
QSTAT(1) User Contributed Perl Documentation QSTAT(1)
NAME
qstat - display job/partition information in a familiar pbs format
SYNOPSIS
qstat [-f] [-a|-i|-r] [-n [-1]] [-G|-M] [-u user_list] [-? | --help] [--man] [job_id...]
qstat -Q [-f]
qstat -q
DESCRIPTION
The qstat command displays information about jobs.
OPTIONS
-a Displays all jobs in a single-line format. See the STANDARD OUTPUT section for format details.
-i Displays information about idle jobs. This includes jobs which are queued or held.
-f Displays the full information for each selected job in a multi-line format. See the STANDARD OUTPUT section for format details.
-G Display size information in gigabytes.
-M Show size information, disk or memory in mega-words. A word is considered to be 8 bytes.
-n Displays nodes allocated to a job in addition to the basic information.
-1 In combination with -n, the -1 option puts all of the nodes on the same line as the job id.
-r Displays information about running jobs. This includes jobs which are running or suspended.
-u user_list
Display job information for all jobs owned by the specified user(s). The format of user_list is: user_name[,user_name...].
-? | --help
brief help message
--man
full documentation
STANDARD OUTPUT
Displaying Job Status
If the -a, -i, -f, -r, -u, -n, -G, and -M options are not specified, the brief single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job name
the job owner
the cpu time used
the job state
C - Job is completed after having run E - Job is exiting after having run. H - Job is held. Q - job is queued, eligible to run or
routed. R - job is running. T - job is being moved to new location. W - job is waiting for its execution time (-a option) to be
reached. S - job is suspended.
the queue that the job is in
If the -f option is specified, the multi-line display format is used. The output for each job consists of the header line: Job Id: job
identifier followed by one line per job attribute of the form: attribute_name = value
If any of the options -a, -i, -r, -u, -n, -G or -M are specified, the normal single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job owner
the queue the job is in
the job name
the session id (if the job is running)
the number of nodes requested by the job
the number of cpus or tasks requested by the job
the amount of memory requested by the job
either the cpu time, if specified, or wall time requested by the job, (in hh:mm)
the job state
The amount of cpu time or wall time used by the job (in hh:mm)
EXIT STATUS
On success, qstat will exit with a value of zero. On failure, qstat will exit with a value greater than zero.
perl v5.14.2 2012-04-10 QSTAT(1)