On Wednesday 29 March 2006 20:53, Kern Sibbald wrote:
> That is either a bug or because the code is unimplemented -- I seem to
> recall that either Max Start Time or Max Run Time was not fully
> implemented.

OK, from a look at the sources I get the impression that MaxStartDelay is
only ever checked when the job really is started. A watchdog ist running,
but apart from the fact that it would only check MaxWaitTime it skips the
job because JobId is 0.

No problem - functionality isn't affected. It just would be nice if the
watchdog could also handle this.

MfG, Ulrich

-- 
Heinz Ulrich Stille / Tel.: +49-541-9400473 / Fax: +49-541-9400450
design_d gmbh / Wilhelmstr. 16 / 49076 Osnabrück / www.design-d.de



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to