Am 21.05.2011 20:49, schrieb Marc Haber: > On Sat, 21 May 2011 17:22:05 +0200, Michael Biebl <firstname.lastname@example.org> > wrote: >> A similar issue (not directly IPv6 related) was discussed on fedora-devel not >> very long ago. It was about the more "dynamic" nature of NetworkManager and how >> certain services currently don't cope with the network not being up and fully >> configured, when they start up.  >> >> See some suggestions how to address this are at . > > That article says that servers should use FREEBIND or subscribe to > netlink for changes. This is a major effort which needs upstream > cooperation or local patches. Depends on what you consider major effort, but yeah, it requires a patch. But I don't see why upstream shouldn't merge such a patch so it should be a one-time effort. It's imho the right way to fix this. Everything else looks like a distro specific hack. > The third option suggests that the network manager option mentioned > there is what one would need for ifupdown, and I don't have the > slightest idea how one could guess whether the networks is "done" now. The third option that was mentioned there, is using the NetworkManager-wait-online.service. This depends on using systemd though. In systemd, services can declare a dependency on "network.target", and the NetworkManager-wait-online.service can block this target until the network is actually up, i.e. NM has established a connection. I don't think it would fix your problem though. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature