Kern Sibbald wrote:
> 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 Concurrent 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.
I wasn't posting this here looking for support. I'd already solved the
problem. I posted it here, to the development list, because it appears
to be a bug - or at least a "doesn't work as anticipated" - in the syntax.
In theory, no Max Concurrent Jobs directive is ignored. In practice, at
least on Solaris 10 x86, if there is no Max Concurrent Jobs directive in
bacula-dir.conf->Storage{}, then a Max Concurrent Jobs directive in
bacula-sd.conf->Storage{} has no apparent effect. If this is not what's
*intended* to happen, then it needs to be looked into.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
[email protected] [email protected] [email protected]
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
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
