|
seems to be a common mis-conception or I'm /much/ luckier than I should be as I routinely run jobs that last over 15-20 days with zero problems (besides them taking 15-20 days. ;) ). I've been doing this for a couple years now end on end with different deployments of bacula (mainly linux/ubuntu server as the host os).
Longest job I have in my current history list is slightly over 30 days. So if there is a limit it's at least much futher out than '5' or the old list comments (circa 2007) of '6'. I'm running 5.0 series of code.
-----Original Message-----
> Does Bacula really kill long running jobs? Or are you seeing the effect
> of something at layer 3 or below (eg TCP connections timing out in
> firewalls)?
>
I believe it automatically kills jobs that are longer than 5 days or
something similar. At least that was discussed recently on the list.
John
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
| 