> So the app appears to be using some internal default, and not actually
> reading the file.
Make sure you specify the full path to the config file through the -c
commandline option. Most likely cause is the fd loading its
configuration from a different file than the one you're looking at
(which i
-Original Message-
From: Andrea Conti
Sent: Wednesday, 14 October 2009 9:46 AM
To: 'bacula-users@lists.sourceforge.net'
Subject: Re: [Bacula-users] Win64 fd: Does not read conf file
> So the app appears to be using some internal default, and not actually >
> re
> So the app appears to be using some internal default, and not actually
> reading the file.
If this is not the first bacula installation on a clean system, make
sure you specify the full path to the config file through the -c
commandline option. Most likely cause is the fd loading its
configurati
Hi,
13.10.2009 16:47, Sean M Clark wrote:
> George Shaw wrote:
>> As far as I can determine, the Win64 bacula-fd service does not actually
>> read the provided conf file. It complains about being unable to read a
>> “monitor_n...@” file on line 35. This is indeed how the default conf
>> file comes
George Shaw wrote:
> As far as I can determine, the Win64 bacula-fd service does not actually
> read the provided conf file. It complains about being unable to read a
> “monitor_n...@” file on line 35. This is indeed how the default conf
> file comes after setup (as listed in bacula-fd.conf.in in t
As far as I can determine, the Win64 bacula-fd service does not actually read
the provided conf file. It complains about being unable to read a
"monitor_name@" file on line 35. This is indeed how the default conf file comes
after setup (as listed in bacula-fd.conf.in in the source tree). But the
