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)
I have it set to the following
0 9 * * 1,3,5 /var/tmp/sys_diag
It ran correctly on Wednesday but did not run on Friday and I am not sure why, does the above appear to be correct? (3 Replies)
Hi,
I need to write a shell script which will run i background and will execute other script only on Mon to Fri 10 AM but not on Sat and Sun.
I am able to set it to run on every day at 10AM but how to make it to run only on Mon to Fri
Thanks,
Firestar. (7 Replies)
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)
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)
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)
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
LEARN ABOUT DEBIAN
globus_gram_protocol_job_state
GRAM Job States(3) globus gram protocol GRAM Job States(3)NAME
GRAM Job States -
Enumerations
enum globus_gram_protocol_job_state_t { GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING = 1, GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE = 2,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED = 4, GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE = 8, GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED = 16,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED = 32, GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN = 64, GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT
= 128, GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL = 0xFFFFF }
Detailed Description
The globus_gram_protocol_job_state_t contains information about the current state of the job as known by the job manager.
Job state changes are sent by the Job Manager to all registered clients. A client may ask for information from the job manager via the
status request.
Enumeration Type Documentation
enum globus_gram_protocol_job_state_t
GRAM Job States.
Enumerator:
GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING
The job is waiting for resources to become available to run.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE
The job has received resources and the application is executing.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED
The job terminated before completion because an error, user-triggered cancel, or system-triggered cancel.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE
The job completed successfully.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED
The job has been suspended. Resources which were allocated for this job may have been released due to some scheduler-specific
reason.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED
The job has not been submitted to the scheduler yet, pending the reception of the GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST
signal from a client.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN
The job manager is staging in files to run the job.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT
The job manager is staging out files generated by the job.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL
A mask of all job states.
Author
Generated automatically by Doxygen for globus gram protocol from the source code.
Version 11.3 Mon Apr 30 2012 GRAM Job States(3)