On Wed, Dec 8, 2010 at 10:38 AM, Camaleón <[email protected]> wrote: > On Wed, 08 Dec 2010 08:37:52 -0500, Tom H wrote: >> On Wed, Dec 8, 2010 at 8:23 AM, Camaleón wrote: >>> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote: > >>>> You didn't disable network-manager. You removed the startup scripts >>>> which were correctly put back by the update. >>>> >>>> Of course I only know this by being bitten by it several times in the >>>> past ;-) >>> >>> Hum... good catch. Let's test it. > > (...) > >>> Now, I restart the system (rebooting...) and check for network manager >>> service, that should have been disabled: >>> >>> t...@debian:~$ /etc/init.d/network-manager status NetworkManager is >>> running. >>> >>> But it is running. >> >> "update-rc.d ... 20..." isn't ging to work with insserv (one reason >> being that it numbers the "/etc/rcX.d" scripts indepedently of you). > > Mmm... man page says by using "defaults" the service should be put in > sequence number 20 (unless there are any conflicts): > > t...@debian:~$ ls -l /etc/rc* | grep network-manager > lrwxrwxrwx 1 root root 25 dic 8 14:12 K01network-manager -> > ../init.d/network-manager > lrwxrwxrwx 1 root root 25 dic 8 14:12 K01network-manager -> > ../init.d/network-manager > lrwxrwxrwx 1 root root 25 dic 8 14:12 S20network-manager -> > ../init.d/network-manager > lrwxrwxrwx 1 root root 25 dic 8 14:12 S20network-manager -> > ../init.d/network-manager > lrwxrwxrwx 1 root root 25 dic 8 14:12 S20network-manager -> > ../init.d/network-manager > lrwxrwxrwx 1 root root 25 dic 8 14:12 S20network-manager -> > ../init.d/network-manager > lrwxrwxrwx 1 root root 25 dic 8 14:12 K01network-manager -> > ../init.d/network-manager > > And so it seems to be :-?
Did you do the above on a Lenny or Squeeze/Sid box? Whenever I use update-rc.d on a sid box to stop/remove/disable, I get a "using concurrency based boot sequencing" message with a warning about runlevels. It's just a warning so I guess that it's OK but I don't like it and now avoid update-rc.d. Furthermore, how does insserv deal with the scripts if you assign S20 to network-manager and it depends on a service that insserv has numbered S21? >> The best way that I've found to deviate from the LSB headers is to use >> "/etc/insserv/overrides/". > > I'll have to test that, but first I would like to know if there is another > method to get the job done. I'd like to understand what I am doing wrong. If you're using Squeeze/Sid and therefore have an insserv-controlled boot-process, why not use an insserv solution? There's more typing to be done but it works. I've just tried "update-rc.d -f remove nfs-kernel-server; update-rc.d nfs-kernel server stop 2 3 4 5 ." and rebooted to find that nfs-kernel-server is still running. I've also just tried "update-rc.d -f disable nfs-kernel-server" and rebooted to find that nfs-kernel-server is still running. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
