On Tuesday 01 November 2005 22:17, Shawn Wilson wrote:
> Ok, after much beating my head against the wall, I figured this thing
> out
>
> ** UNDOCUMENTED RULE NUMBER 1
>
> NEVER, EVER, EVER, EVER INSTALL THE WIN32 CLIENT TO THE F: DRIVE!
> IT DOES NOT WORK
D
Ok, after much beating my head against the wall, I figured this thing
out
** UNDOCUMENTED RULE NUMBER 1
NEVER, EVER, EVER, EVER INSTALL THE WIN32 CLIENT TO THE F: DRIVE!
IT DOES NOT WORK
* ONLY INSTALL TO THE C: DRIVE!!! *
>Kern Sibbald wrote
I actually ran into the same issue just yesterday.
Try putting an explicit drive letter in front of the WorkingDirectory and Pid
Directory locations in the bacula-fd.conf file. That fixed it for us.
-Brian
Quoting Shawn Wilson <[EMAIL PROTECTED]>:
Has anyone been able to get the bacula-fd se
Kern Sibbald wrote:
> On Wednesday 26 October 2005 17:15, Shawn Wilson wrote:
>
>>Has anyone been able to get the bacula-fd service to work on a win2k3
>>server? I ran the default install routine and had it install itself as
>>a service but when I run 'netstat -an', nothing is listening on port
>
tober 26, 2005 11:41 AM
To: bacula-users@lists.sourceforge.net
Cc: Shawn Wilson
Subject: Re: [Bacula-users] bacula-fd service doesn't respond
On Wednesday 26 October 2005 17:15, Shawn Wilson wrote:
> Has anyone been able to get the bacula-fd service to work on a win2k3
> server? I ran the default instal
On Wednesday 26 October 2005 17:15, Shawn Wilson wrote:
> Has anyone been able to get the bacula-fd service to work on a win2k3
> server? I ran the default install routine and had it install itself as
> a service but when I run 'netstat -an', nothing is listening on port
> 9102. I check the task
