I know you can set up jobs with a across-director priority number,
but I'm wondering if it is possible to prioritize jobs on a per-
client basis. Specifically, I have job(defs) for job A and job B, and
I need A jobs to always run before B jobs for each.
Currently I have them set to different priority and schedule levels.
While this prevents any "B before A" situations, it also means that
*no* job B's can run before *all* job A's are complete, which means
one server that takes a while with job A can hold up job B on every
client machine.
While I could have job B check (via runscript) if Job A was already
run on the client and have it error out with a reschedule interval...
this seems like quite a bit of a kludge, especially if I tack on jobs
C and D, etc.
--
--Darien A. Hager
[EMAIL PROTECTED]
Mobile: (206) 734-5666
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
