Op 8/05/2012 11:06, Silver Salonen schreef:
> Hi.
>
> Does anyone know how to interpret Max Time directives from 
> http://www.bacula.org/en/dev-manual/main/main/New_Features_in_3_0_0.html#SECTION00132417000000000000000
>  ?
>
> Should the "Max Run Time" indicate "Run Time" + "Blocked" (Max Wait Time) + 
> "Run Time"?
> Also, "Max Run Sched Time" is said to be "Max Start Delay + Max Run Time", 
> but on the drawing it ends with the 1st "Run Time" and thus lasts until the 
> the job starts waiting for something.
>
 From experience I know that "Max Run Sched Time" is the time between 
the scheduled time of the job and when it gets cancelled. It doesn't 
matter if it's waiting for something or if it's actually running. If the 
job is still "alive" in a way after the "Max Run Sched Time" has passed 
the director will cancel it.

"Max Run Time" only starts counting from when the job actually starts 
running. So the time it waits from the scheduled time before actually 
running (waiting for other jobs, waiting for storage, ...) isn't taken 
into account.

Regards,
Jeremy

 **** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users