On 06/01/2010 10:59 AM, Teodor wrote:
Package: bacula-director-mysql
Version: 5.0.1-1~bpo50+1
Severity: normal
Hi,
The "Max Run Time" directive for Bacula Director is described at [1] like this:
| Max Run Time = time
| The time specifies the maximum allowed time that a job may run, counted from
| when the job starts, (not necessarily the same as when the job was
scheduled).
However, the job start is something like 10 seconds from the scheduled time even
if the job never starts due to waiting in the queue of SD. The end result is
that
even if the job never runs, the job is cancelled after the time expires as if
"Max Run Sched Time" was specified instead of "Max Run Time". See attached a log
for such a job as an example.
Hi Teodor,
This is probably a support question for upstream -- is the documentation
wrong or is the code wrong, or is there something else in your
configuration causing the problem? They have a mailing list that I'd
recommend you send this to.
-- John
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
