Eric
You may want to look at
Max Start Delay = NN hours etc
The job must start in NN hours from when scheduled or it will be canceled.
Stephen Carr
Eric Piollet wrote:
> Ok thanks a lot !!!
> With only this parameter "Max Run Time = 1h", my job is cancelled after
> 1 hour
>
>
>
> Aaron Kniste
Ok thanks a lot !!!
With only this parameter "Max Run Time = 1h", my job is cancelled after
1 hour
Aaron Knister a écrit :
> Uncomment the following line-
>
> #Max Run Time = 1h
>
> I believe this defines the maximum amount of time the job will run.
> However if the job is running and goes f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suspect the original poster will then ask "well, so then what is
MaxWaitTime for? I'm not 100% certain, but I suspect that this is for
jobs that cannot exec because their priority is too low, a device is
busy, or something like that.
I would submit
Uncomment the following line-
#Max Run Time = 1h
I believe this defines the maximum amount of time the job will run. However if
the job is running and goes for longer than 2 hours it will be killed. You may
want to edit your "RunBeforeJob" script to check for the tape "mt -f /dev/nst0
status"
