Re: [Bacula-users] Redundant Run in Schedule

2008-02-25 Thread Bastian Friedrich
Hi, I'll keep my answer on this subject short, as you are obviously currently working on the topic in a larger scope; I'll add some comments on your new thread on bacula-devel. On Friday 22 February 2008, Kern Sibbald wrote: > On Friday 22 February 2008 15.44:56 Bastian Friedrich wrote: > > > >

Re: [Bacula-users] Redundant Run in Schedule

2008-02-22 Thread Kern Sibbald
On Friday 22 February 2008 15.44:56 Bastian Friedrich wrote: > Hi, > > On Wednesday 20 February 2008, Bastian Friedrich wrote: > > 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

Re: [Bacula-users] Redundant Run in Schedule

2008-02-22 Thread Bastian Friedrich
Hi, On Wednesday 20 February 2008, Bastian Friedrich wrote: > 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 tha

Re: [Bacula-users] Redundant Run in Schedule

2008-02-21 Thread Bastian Friedrich
Hi, On Thursday 21 February 2008, Arno Lehmann wrote: > It *might* be possible using a python event Interesting idea; regarding the unknown future of the python support, I'd rather not invest too much time there, though. > > On the other hand, as I said: the problem can be circumvented with a >

Re: [Bacula-users] Redundant Run in Schedule

2008-02-21 Thread Arno Lehmann
Hi, 20.02.2008 21:41, Bastian Friedrich wrote: > Hi, > > On Mittwoch 20 Februar 2008, Arno Lehmann wrote: >> 20.02.2008 15:31, Bastian Friedrich wrote: >>> [...] it is not >>> difficult to circumvent, either: >>> Run = Full Pool = PoolSpecial w01 mon at 8:00 >>> Run = Full Pool = Pool w01 w02

Re: [Bacula-users] Redundant Run in Schedule

2008-02-20 Thread Bastian Friedrich
Hi, On Mittwoch 20 Februar 2008, Arno Lehmann wrote: > > 20.02.2008 15:31, Bastian Friedrich wrote: > > [...] 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 on

Re: [Bacula-users] Redundant Run in Schedule

2008-02-20 Thread Arno Lehmann
Hi, 20.02.2008 15:31, Bastian Friedrich wrote: > 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 r