View Issue Details

IDProjectCategoryView StatusLast Update
0000924bareos-core[All Projects] documentationpublic2019-11-07 18:26
ReportertuxmasterAssigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSCentOSOS Version7
Product Version17.2.5 
Fixed in Version 
Summary0000924: Absolute Job Timeout option for the director settings is not described
DescriptionNether the default settings nor the meaning of it are documented.

Only this little text are present:
Absolute Job Timeout = <positive-integer>
Version >= 14.2.0
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

b.braunger@syseleven.de

b.braunger@syseleven.de

2019-11-07 18:26

reporter   ~0003616

Explained here: https://bareos-users.narkive.com/Mtv7pNGw/absolute-job-timeout

> Absolute Job Timeout was added to 14.2 to replace the Bacula hard coded
> limit of 6 days for a Job which some people ran into when doing long running
> jobs. Its now by default set to 0 which means don't care about how long a Job runs.
> But if you have the idea you have the need to automatically kill jobs that run
> longer then this is known to work well in Bacula as all jobs longer then 6 days
> got nicely killed there. Given you can properly cancel Jobs I see no real reason
> to set it that is also why the new default is 0 and not the old arbitrary 6 days.

Issue History

Date Modified Username Field Change
2018-03-03 15:34 tuxmaster New Issue
2019-11-07 18:26 b.braunger@syseleven.de Note Added: 0003616