0000924: Absolute Job Timeout option for the director settings is not described

ID	Project	Category	View Status	Date Submitted	Last Update

0000924	bareos-core	documentation	public	2018-03-03 15:34	2023-09-12 15:20

Reporter	tuxmaster	Assigned To	bruno-at-bareos
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Platform	Linux	OS	CentOS	OS Version	7
Product Version	17.2.5

Summary	0000924: Absolute Job Timeout option for the director settings is not described
Description	Nether 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
Tags	No tags attached.

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.

bruno-at-bareos 2023-07-20 17:15 manager ~0005242	nobody brave enough to make a doc PR ?

bruno-at-bareos 2023-09-12 15:20 manager ~0005416	Fixed in PR1543

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
2023-07-20 17:15	bruno-at-bareos	Note Added: 0005242
2023-09-12 15:19	bruno-at-bareos	Assigned To	=> bruno-at-bareos
2023-09-12 15:19	bruno-at-bareos	Status	new => assigned
2023-09-12 15:20	bruno-at-bareos	Status	assigned => closed
2023-09-12 15:20	bruno-at-bareos	Resolution	open => fixed
2023-09-12 15:20	bruno-at-bareos	Note Added: 0005416