> 1. Allow Duplicate Jobs = Yes | No | Higher (Yes) Looks OK. One question: if a lower level job is running, and a higher level job attempts to start, does this imply that the lower level job is cancelled, and the higher level one is run instead? I think this is desirable behavior if possible (or maybe it might require an additional option of Supercede for this directive to enable this behavior). > 2. Duplicate Job Interval = <time-interval> (0)
The semantics look fine, but a usability suggestion: Since you're really setting a proximity guard interval, it might be easier to understand for the end user if you used Duplicate Job Proximity rather than Interval. That would give the implication of "no closer than" that I think you want, and it might translate better. > PS: I think the default for Allow Duplicate Jobs should be Higher, but > that > would change current behavior ... I agree with you. It's dumb to do an incremental followed immediately by a full backup if they're going to dump the same data in roughly the same timeframe. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
