On 03/02/11 05:24, Raphael Geissert wrote: > Interesting that everyone talks about update-rc.d but it appears that nobody > has read its documentation: > >> A common system administration error is to delete the links with >> the thought that this will "disable" the service, i.e., that this will >> prevent the service from being started. However, if all links have >> been deleted then the next time the package is upgraded, the package's >> postinst script will run update-rc.d again and this will reinstall links >> at their factory default locations. The correctc way to disable >> services is to configure the service as stopped in all runlevels in >> which it is started by default. In the System V init system this means >> renaming the service's symbolic links from S to K. > > That means: > # mv /etc/rc2.d/S??apache2 /etc/rc2.d/K00apache2 > # insserv # this bit is not documented, it seems
Are you serious? How's that a sysadmin interface? Yes, everything can be done using sh/cp/mv/vi, but this is hardly something that's either properly documented or a replacement for the current method of doing things. Also, while we're at update-rc.d's documentation, that particular manpage says: > Example of disabling a service: > update-rc.d -f foobar remove > update-rc.d foobar stop 20 2 3 4 5 . Have you tried that recently? It doesn't work in squeeze systems. On the other hand, update-rc.d has enable/disable since squeeze, but this is considered an unstable interface, AFAIK. Regards, Faidon -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d6e4944.90...@debian.org
