On Tue, Jul 16, 2013 at 02:17:57PM -0700, Steve Langasek wrote: > On Tue, Jul 16, 2013 at 08:29:44PM +0100, Roger Leigh wrote: > > On Tue, Jul 16, 2013 at 11:33:37AM +0200, Daniel Baumann wrote: > > > I don't see what could be done in tftp-hpa to address the issue, it > > > declares the network depends in the lsb header of the sysvinit script; > > > if sysvint then doesn't do the right thing (anymore) when NM is > > > installed, then this is either a bug in NM or in sysvinit, reassigning > > > to sysvinit. > > > Does > > > echo '$network network-manager' > /etc/insserv.conf.d/network-manager > > insserv > > > fix things; or alternatively > > > edit /etc/insserv.conf to read > > $network +networking +ifupdown +network-manager > > run insserv > > No, because this only determines that the network-manager daemon is started > before those services that require a network; it says nothing about the > network connection being brought up.
Shouldn't the network-manager init script be blocking until that's happened? Isn't that one of the guarantees which $network should be providing? At least, if it was claiming to provide $network which it currently doesn't. As it is, network-manager only requires: # Required-Start: $remote_fs dbus udev # Required-Stop: $remote_fs dbus udev # Should-Start: $syslog # Should-Stop: $syslog So it's not clear to me how any service depending on $network would guarantee any networking when using network manager--it could be ordered after any of these services. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
