I don't see any reason to change the current behavior. It may be a bit
difficult to get used to it, but the different Max Councurrent Jobs all have
different actions, and none are ignored.
My recommendation is to carefully read the manual, then if you have questions,
please ask on the bacula-users list where they help with these kinds of
problems (support). On this list, we deal only with development issues so we
do not have the same ability to respond to these kinds of problems and
questions.
Best regards,
Kern
On Tuesday 12 May 2009 02:56:34 Phil Stracchino wrote:
> I've just spent two hours going nuts trying to get concurrent jobs
> running on my new 3.0.1 install on my new server, because of an
> oversight in the config file syntax and syntax checking.
>
>
> Here's the problem:
>
> The "Max Concurrent Jobs" directive is *legal* in the Storage resource
> in bacula-dir.conf, but is not *required* there, so it's not reported as
> an error if it's missing.
>
> The "Max Concurrent Jobs" directive is *ALSO* legal in the Storage
> resource in bacula-sd.conf, but there, it is *ignored*, and not reported
> as an error if it's present.
>
> So, you set director concurrency to 20 in bacula-dir.conf, you set
> storage concurrency to 20 in bacula-sd.conf which seems quite reasonable
> and logical, you run <daemon> -t to check the syntax and it says the
> good, then you start everything and try to run two concurrent jobs ...
> and it doesn't work. But everything in the configuration looks as
> though it should. It's not at all obvious that the sd has ignored the
> concurrency setting, and the dir has silently defaulted it to 1.
>
>
> My suggestion: Since Max Concurrent Jobs is ignored in bacula-sd.conf's
> storage{}, make <bacula-sd -t> report it as an error and emit a message
> along the lines of "This directive must go in the Director's Storage
> resource." Make it REQUIRED in bacula-dir.conf's storage{}, even if
> explicitly set to 1.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel