[pkg-bacula-devel] Bug#584135: bacula-director-mysql: "Max Run Time" directive does not work as described

[Alexander Golovko]

tags 584135 + upstream
found 584135 5.2.6+dfsg-2
found 584135 5.0.2-2.2
forwarded 584135 http://bugs.bacula.org/view.php?id=1908
thanks
--

Hi, Teodor!

Thank you for your bug report and sorry for delay.

This bug look like it still present in last packaged in debian version 
(5.2.6+dfsg-2)

There was created report in upstream bugtracker:
http://bugs.bacula.org/view.php?id=1908


On Tue, 01 Jun 2010 18:59:14 +0300, 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.
>
> Thanks
>
> [1] 
> http://www.bacula.org/5.0.x-manuals/en/main/main/Configuring_Director.html
>
>
> -- System Information:
> ...


-- 
with best regards,
Alexander Golovko
email: alexandro at ankalagon.ru
xmpp: alexandro at ankalagon.ru