On 08/07/2017 10:09 PM, Phil Stracchino wrote:
> On 08/08/17 00:03, Bill Arlofski wrote:
>> On 08/05/2017 04:08 PM, Phil Stracchino wrote:
>>> Did I forget somewhere I need to set that? The Client resource in
>>> bacula-dir.conf doesn't need a Maximum Concurrent Jobs directive ...
>>> does it?
>>
On 08/05/2017 04:08 PM, Phil Stracchino wrote:
> A new client recently first added with 9.0.2 seems to have its maximum
> job concurrency set to 1 despite explicitly setting it to 20:
>
> FileDaemon {
> Name = asgard-fd
> FDport = 9102
> WorkingDirectory = /opt/bacula/var
> Pid Directory =
On 08/08/17 00:03, Bill Arlofski wrote:
> On 08/05/2017 04:08 PM, Phil Stracchino wrote:
>> Did I forget somewhere I need to set that? The Client resource in
>> bacula-dir.conf doesn't need a Maximum Concurrent Jobs directive ...
>> does it?
>
> Hi Phil,
>
> Yes, as a matter of fact, there is a
On 08/05/2017 04:08 PM, Phil Stracchino wrote:
> A new client recently first added with 9.0.2 seems to have its maximum
> job concurrency set to 1 despite explicitly setting it to 20:
>
> FileDaemon {
> Name = asgard-fd
> FDport = 9102
> WorkingDirectory = /opt/bacula/var
> Pid Directory =
A new client recently first added with 9.0.2 seems to have its maximum
job concurrency set to 1 despite explicitly setting it to 20:
FileDaemon {
Name = asgard-fd
FDport = 9102
WorkingDirectory = /opt/bacula/var
Pid Directory = /var/run
Maximum Concurrent Jobs = 20
Plugin Directory = /
