 |
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. |
- Anonymous
