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 then I
commented out all those lines defining a local director for the tray, as there
is none in Win64. And still the error persists when trying this in -t mode from
cmd. Just for fun, I rebooted the server to no avail. There is no other .conf
file on the entire server.
So the app appears to be using some internal default, and not actually reading
the file.
To prove this assertion, I added the line "bonk" at the top of the conf file.
No change in the error output.
A win32 fd-only setup works fine.
Maybe I'm missing something obvious.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
