On 8/26/07, James Harper <[EMAIL PROTECTED]> wrote: > I had the following configuration: > > " > Director > Max Concurrent Jobs = 1 > > Job1 > Client = Client1 > Storage = Storage1 > > Job2 > Client = Client2 > Storage = Storage2 > " > > Then it occurred to me that it would be perfectly reasonable to run 2 > jobs at the same time if they were both using completely different > Client and Storage resources, so I set Max Concurrent Jobs = 2 in the > Director and issued a 'reload'. But Job1 and Job2 don't seem to run > concurrently. If I start Job1 and then Job2, Job2 sits at "waiting > execution". > > My questions are: > > 1. Should Job1 and Job2 run concurrently after the configuration change, > or is there something I've overlooked? > You need to set this in at least 4 places. See the reply from Arno in the following thread: http://sourceforge.net/mailarchive/forum.php?thread_name=200708071029.59327.bacula%40kopecki.net&forum_name=bacula-users
> > 2. Is a reload sufficient, or do I need to restart the director to make > this change take effect? > A reload is sufficient. John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
