From: Kjetil T. H. <kje...@li...> - 2008-10-06 13:26:01
|
Alan Brown <aj...@ms...> writes: > On Mon, 6 Oct 2008, Kjetil Torgrim Homme wrote: > >> This directive is only implemented in version 2.5 and later. When >> set to {\bf yes} (default {\bf no}), this job may run even if lower >> priority jobs are already running. This means a high priority job >> will not have to wait for other jobs to finish before starting. >> The scheduler will only mix priorities when all running jobs have >> this set to true. > > There are some jobs which _must_ run exclusively for whatever reason. > > BackupCatalog is one of them. > > If you allow mixed priority jobs to run simultaneously, you also > need some way of flagging a job as "exclusive" this is accomplished by not setting Allow Mixed Priority on BackupCatalog. (also, you should set BackupCatalog to have a unique priority among the jobs in your configuration -- but this is true regardless of whether Allow Mixed Priority is set or not.) -- regards, | Redpill _ Kjetil T. Homme | Linpro (_) |