The description of the priority option for Job says that "If by chance Bacula treats a lower priority first, then it will run before your high priority jobs. To avoid this, start any higher priority a few seconds before the lower ones."
I don't understand what good priorities do then. If I schedule the jobs in the sequence I want them to run, that alone should determine their sequence (at least if I follow the recommendation for one job at a time). The discussion seems to imply that priority is relevant both with and without concurrent jobs. Second, is there any easy way to vary the scheduling of jobs by a few seconds, other than writing a completely new schedule? This seems a maintanence headache. My hope was that if I wanted to control the order of execution of jobs I could give them the same schedule and different priorities. Finally, the language is a bit unclear, though I think I know what's intended. For "treats" I read "processes," and I insert "jobs" after "start any higher priority". Thanks. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
