On Tue, May 12, 2009 at 9:48 AM, Phil Stracchino wrote:
> John Drescher wrote:
>>> This is how it is documented to work in the manual.
>>>
>> I do admit that this is not easy to find because you have to read each
>> section and the bacula-dir.conf settings override bacula-sd.conf and
>> bacula-fd.
John Drescher wrote:
>> This is how it is documented to work in the manual.
>>
> I do admit that this is not easy to find because you have to read each
> section and the bacula-dir.conf settings override bacula-sd.conf and
> bacula-fd.conf settings for the case of 1 director.
Then why don't we pro
> This is how it is documented to work in the manual.
>
I do admit that this is not easy to find because you have to read each
section and the bacula-dir.conf settings override bacula-sd.conf and
bacula-fd.conf settings for the case of 1 director.
In bacula-dir.conf you have Maximum Concurrent Job
> It may default to 20 *there*, but that seems to be overridden by what's
> set in the Storage resource in bacula-dir.conf, and if *that's* omitted,
> it apparently defaults to 1.
There is an independent setting in the Storage resource in
bacula-dir.conf for the that as well. The same goes for the
On Mon, May 11, 2009 at 8:56 PM, 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 Concurren
