Hi list,

today one job failed with "max run time exceeded",
this job is configured with "max run time = 20mins" and
was scheduled for 12:05.
due to some small problems it took some time to get the tapedrive ready.
the job was cancelled at 12:25 after 2 minutes of run time:

2009-01-14 12:21:40     Volume "TMDA02" previously written, moving to end of 
data.
2009-01-14 12:23:31     Ready to append to end of Volume "TMDA02" at file=81.

....

2009-01-14 12:25:37     Fatal error: Max run time exceeded. Job canceled.

i think the time to get the drive ready,
e.g. if intervention is needed (label a new volume for pool ...),
should not count for the run time.

this time should be something for the "max start delay",
which is not configured in this case, shouldn't it?

Regards
Thomas
-- 
[:O]###[O:]

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users