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