On Vi, 09 mai 14, 09:19:55, Mihamina Rakotomandimby wrote: > Hi all, > > A long time ago, when I was young ;-), services used to be managed with > "invoke-rc.d" & "update-rc.d" on Debian. > > Know playing with several distributions, some use "service", "sysctl", > "systemctl", and some of them are mentionned for managing services in > Debian. > > Typically, on a Debian when I "a2ensite", there is a message indicating to > "service apache2 reload" in order to fullfill the new VirtualHost > consideration. > > I would like to stick with the "native" tools for each distribution I > manage: On Wheezy what is the right one? What is wrapping what? As far as I know both 'service' and 'update-rc.d' have been updated to do the right thing depending on how you boot (sysv-rc, systemd, etc.). There is also a feature request for 'service' to do 'disable' as well, but hasn't been implemented yet. As another poster already demonstrated, beware of 'update-rc-d remove', as the manpage warns: ,----[ update-rc-d(8) ] | 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 correct 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. `---- Hope this helps, 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
Attachment:
signature.asc
Description: Digital signature