On Wed, Oct 05, 2005 at 11:42:09AM +0100, Russell Howe wrote: > Ross Boylan wrote: ... > > Given jobs scheduled at different times, does priority add anything to > > when they are run? > > If a higher priority job is running, a lower priority job will not start. > > "higher priority" means a low value for Priority > "lower priority" means a higher value for Priority
If you only allow a single job to run at a time, whichever starts first runs first and will complete before the next job. So it sounds as if priority matters under two scenarios 1) concurrent jobs allowed (which is what most of the snipped discussion concerns). Priorities can guarantee that certain waves of jobs will finish completely before other start. Without priorities, a lower priority job might start while a higher priority one is running (high priority = low priority number), even if the start time of that job is scheduled later. 2) single jobs. Priorities may influence which of several simultaneously scheduled jobs start first, but this is not completely reliable. Am I following correctly? Ross ------------------------------------------------------- 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
