* James Harper schrieb am 26.08.07 um 14:56 Uhr:
> 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".
I have the same problem.
One director, but two jobs that use completely different FD and SD
do not run parallel, ("Maximum Concurrent Jobs = 10" in
bacula-dir.conf's Director{} stanza)
I tried several things but I would assume that concurrency for those
kind of jobs should *always* run in parallel or at least if the
central "Maximum Concurrent Jobs" in bacula-dir.conf is >1
Which behavior is expected?
thanks in advance
-Marc
--
BUGS My programs never have bugs. They just develop random
features. If you discover such a feature and you want it to
be removed: please send an email
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
