Alan, thanks, i know bacula cant run different priority jobs 
concurrently. Moreover, since each of my clients has a separate pool, I 
couldn't have concurrent jobs anyway.

My issue still remains unsolved, however. I guess the only way to get 
around it is to have multiple schedules. And all I want to do is to have 
each job run one by one!
Max Run Time is only there to make sure that if a job stalls, other jobs 
in the queue wont be blocked until i intervene.

I do think though, that Max Run Time section in the manual should be 
changed. It does sound ambiguous, because "Max Run Time" timer 
apparently starts as the job is _queued_, and not _started_, as it is 
stated in the manual.

Cheers,
Mantas




Alan Brown wrote:
> On Tue, 27 May 2008, Mantas M. wrote:
> 
>> Last night I've altered my bacula configs and gave each job a different
>> priority. After that, i noticed, that bacula no longer says "waiting for
>> higher priority jobs to complete", and just says "waiting for execution"
>> for jobs, with lower priority.
> 
> Jobs with differing priorities can't run concurrently.
> 
> Jobs with higher priorities won't usurp currently running jobs, but they
> will slot in the queue immediately behind the running ones and all other
> queued jobs will have to wait for those higher priority jobs to finish.
> 
> 
> 


-------------------------------------------------------------------------
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 AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users