On Sb, 22 nov 14, 17:53:09, Jean-Marc wrote: > hi everybody, > > I disabled NFS yesterday using a <systemctl disable nfs-common.service>. > > The output I got was OK, displaying the whole bunch of messages saying it > updated symlinks using <update-rc.d>. > > But today, it restarted. And it is normal: the symlinks are still there. > > I re-did again verifying the symlinks and they stay unchanged. > > Something wrong with my Jessie system ?
As far as I can tell this is because of the headers in
/etc/init.d/nfs-common:
# Default-Start: S
# Default-Stop: 0 1 6
If you previously had S links in other runlevels than S as far as I
understand update-rc.d should not touch them. You should be able to fix
this with
update-rc.d nfs-common remove
update-rc.d nfs-common defaults
update-rc.d nfs-common disable
Beware I just tried this on my system (sid) and got... interesting
results. I had to run the 'remove' and 'defaults' twice to get the
desired results. Might be a strange interaction with the previous run of
'systemctl disable nfs-common'.
According to the changelog nfs-common was switched to only start in
runlevel S as of version 1:1.2.8-6. I'm guessing it didn't also remove
old (now obsolete) symlinks. If my theory is correct you should probably
report this as a bug against nfs-common.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt
signature.asc
Description: Digital signature
