[pkg-bacula-devel] Bug#679479: Bug#679479: bacula-fd fails to start because network is not initialized

[Tom Epperly]

>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 "fix" was to add delays to the bacula init script to make sure
netmanager was done.

Tom

On Mon, Dec 1, 2014 at 1:24 PM, Geert Stappers <stappers at stappers.nl> wrote:

> On Mon, Dec 01, 2014 at 01:04:34PM -0800, Tom Epperly wrote:
> > On Mon, Dec 1, 2014 at 10:41 AM, Carsten Leonhardt <leo at 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
> > > your bacula-fd.conf?
> > >
> > > Just omitting the directive should (have) give(n) you a functioning
> > > backup.
> > >
> >
> > I think I based my configuration file on the documentation and examples
> > that were available at the time.
> >
>
> What could (should?) be done to avoid that other people
> encounter the bug that you reported?
>
>
>
> Groeten
> Geert Stappers
> --
> Leven en laten leven
>
> --
> To unsubscribe, send mail to 679479-unsubscribe at bugs.debian.org.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20141201/d714994d/attachment.html>