On Mon, Dec 01, 2014 at 01:04:34PM -0800, Tom Epperly wrote:
On Mon, Dec 1, 2014 at 10:41 AM, Carsten Leonhardt l...@carotec.de wrote:
Dear Tom,
is (or was, as your bug report is over 2 years old now) there a specific
reason why you had the FDAddress = faerun.epperly.home directive in
From my perspective, it seems like there must be a class of system services
that need to be started after the network is configured and DNS is
available. Bacula and other members of that class of services should have
a common mechanism to be started after network+DNS are available.
I think my
Hi!
Sorry for reply delay.
There is not a bug, so all we can do - add some information about this
case into README.Debian.
You can try one of next workarounds:
1. Allow bacula-fd to listen on all addresses - remove line FDAddress
= .. or change it to FDAddress = 0.0.0.0
2. If you
Thanks for your reply. I understand from a developer's perspective that
there is no bug.
Somewhere along the line, I believe a Debian upgrade switched me from using
/etc/network/interfaces and ifupdown to using NetworkManager. It happened a
while ago, so I don't remember how it all happened. At
4 matches
Mail list logo
