Hello, Of course anything that would improve Bacula is possible. Concerning possible source code changes that do what you call exponential back-off, it is not something that I have on my personal agenda.
Unfortunately normally what happens is that someone develops new code and then submits it. This is not the best approach because if the feature or design is not appropriate for Bacula, the code may not be accepted for inclusion in Bacula. A far better procedure would be for some person to design the feature, submit the design to the project, get the design approved, then implement and submit the code. Best regards, Kern On 9/26/19 2:41 PM, Gary R. Schmidt wrote: > On 26/09/2019 18:37, Kern Sibbald wrote: >> See below ... >> >> On 9/25/19 7:38 PM, Andrea Venturoli wrote: > [SNIP] >>> >>> Yes: as I said it's not a big problem, just an annoyance. >>> *Not* solving the resource contention problem, but just avoiding to >>> nag about it would probably be enough (at least to me). >> >> Bacula is not capable of solving resource contentions itself other than >> trying again. > > Would it be very difficult to change Bacula so that rather than trying > every five (or whatever) minutes it did an exponential back-off? > > Such as, after the first failure try again in five minutes, then again > in fifteen, then in sixty minutes, then two hours, four, eight, > sixteen, too many retries I am giving up? > > I don't think this change would be simple, but I think it should be > possible. > > Cheers, > Gary b-) > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
