On Feb 17, 2008, at 11:03 PM, James Harper wrote: >> >> Unless you are allowing more than one concurrent job. In which case, >> priority will >> be your best bet. But I don't recall you mentioning concurrent jobs. >> > > Hmmm... forgot to mention that :) > > Yes, I'm running the jobs concurrently, so I assume that given an > equal > priority, whichever one finishes writing to the spool will get > despooled > first and finish first, even if it didn't start first?
I have not worked with concurrent jobs. They are... too complex/ risky for my liking. This does not mean I think there is a problem with the code. I just prefer not to use them. As to your question, I don't know.... it's too early in the day. :0 Back to your original question. The subject states "multiple storages". Is the scenario: two jobs, two storage daemons? Or two jobs, one SD? -- Dan Langille -- http://www.langille.org/ [EMAIL PROTECTED] ------------------------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
