Hello Thomas, On 03/13/2013 01:49 PM, Thomas Lohman wrote: >> I have the impression that the original MaxRunSchedTime doesn't handle >> correctly the reschedule option, so it sounds to be better to fix the >> existing directive rather than adding a new directive. >> >> The original goal of this directive was to take the initial schedule run >> time in account to stop the job, and this is exactly what you need. >> >> Do you see any reason to not fix the MaxRunSchedTime ? (maybe some weird >> cases?) > > Hi Eric, no, I can't think of any reason not to change the > MaxRunSchedTime to behave in this manner. I didn't make that change > initially because I wasn't sure of MaxRunSchedTime's original intent and > didn't want to change it's behavior. I can see about altering my > changes to change MaxRunSchedTime instead and re-submit the patch if > that would help.
Yes, such patch would definitely help, I looked quickly your first patch, and it was reasonable. If the patch contains more than few lines (not very likely), we will need also a FLA to include your work. http://www.bacula.org/en/?page=fla Thanks, Bye -- Need professional help and support for Bacula ? Visit http://www.baculasystems.com ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
