This isn't specific to OS X, but once I did burn a bit of time solving
similar symptoms.
On one occasion I used the fqdn in the local conf file, but the director
was configured with the hostname. I use local host files with both for
my bacula boxes. But, when I captured the traffic I saw that
Hi,
On 10/20/2006 8:02 AM, Jens Classen wrote:
> Don wrote:
>
> > Hi Jens,
> >
> > I have the same problem with one of my OS X servers. But on mine, in
> > spite of the error message, the daemon *is* running. The backups run
> > well and I have no other problems.
> >
> > On my other OS X
Don wrote:
> Hi Jens,
>
> I have the same problem with one of my OS X servers. But on mine, in
> spite of the error message, the daemon *is* running. The backups run
> well and I have no other problems.
>
> On my other OS X servers I don't have this problem. However, I did
> not
> co
Hi Jens,
I have the same problem with one of my OS X servers. But on mine, in
spite of the error message, the daemon *is* running. The backups run
well and I have no other problems.
On my other OS X servers I don't have this problem. However, I did not
compile the daemon on each of them. I
Hello there!
I try to set up a bacula environment at work and have the server side
(UNIX) running (means backing up on the server machine with the local fd
works). As next step I wanted to add a 2nd client, which is my Mac
workstation. I configured the config files and compiled a bacula-fd from
th
