Hi, when configuring multiple "Run"s in a schedule that occur at the same time, they are run sequentially: Run = Full Pool = PoolSpecial w01 mon at 8:00 Run = Full Pool = Pool mon at 8:00 results in two executions of the job that refers to the schedule.
This definitely is not a bug, or out of specs; normally, it is not difficult to circumvent, either: Run = Full Pool = PoolSpecial w01 mon at 8:00 Run = Full Pool = Pool w01 w02 w03 [...] w53 mon at 8:00 runs the second job only if the first job is not run. I'd have a need for exclusiveness in this case: run the job only in case it is not referenced before. Would you also regard this as a sensible modification? Maybe we (one? Kern? erm... whoever :) could add a "ElseRun" statement or similar that does not run multiple jobs in one schedule? Is there any more simple solution? Thx Bastian -- Collax GmbH . Burkheimer Straße 3 . 79111 Freiburg . Germany p: +49 (0) 761-45684-24 f: +49 (0) 761-45684-10 www.collax.com Geschäftsführer: William K. Hite / Boris Nalbach AG München HRB 158898 . Ust.-IdNr: DE 814464942 \ 10.0 times 0.1 is hardly ever 1.0. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
