This report only makes sense IF you configured BindAddress manually to use a specific interface AND if some bug in init system attempted to start apt-cacher-ng before the interface is up AND something in the init system has hidden the resulting error message from you.
I don't see what I can do about that right now except of some ugly linux specific workaround waiting for udev/dbus events to reconfigure the interfaces. Let's see what Ubuntu masters propose to fix that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998937 Title: apt-cacher-ng not running at boot up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/998937/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
