On 2014-04-09 22:53, Richard Brown wrote:
On 9 April 2014 18:28, Roman Drahtmueller <draht@suse.de> wrote:
Having an init script and not needing it is better than needing it and not having it. Apparently, it doesn't harm, but rather helps.
I disagree - having both the systemd service file and the /etc/init.d file present on an installed machine causes confusion, both at a system level (eg. different answers to /etc/init.d/SuSEfirewall2 status and systemctl status SuSEfirewall) and at a sysadmin level ("What command do I use to do X?" - we don't want to have 2 different commands with 2 different results serving the same purpose)
Notice that there is no "/etc/init.d/SuSEfirewall2" file. Telcontar:~ # ls /etc/init.d/* | grep -i fire Telcontar:~ # There is this, instead: Telcontar:~ # l /sbin/rcSuSEfirewall2 lrwxrwxrwx 1 root root 25 Feb 25 22:08 /sbin/rcSuSEfirewall2 -> /usr/sbin/rcSuSEfirewall2* Telcontar:~ # l /usr/sbin/rcSuSEfirewall2 lrwxrwxrwx 1 root root 7 Feb 25 22:08 /usr/sbin/rcSuSEfirewall2 -> service* Telcontar:~ # Telcontar:~ # l /usr/sbin/service -rwxr-xr-x 1 root root 3649 Jan 27 09:33 /usr/sbin/service* Telcontar:~ # rpm -qf /usr/sbin/service aaa_base-13.1-16.34.1.x86_64 Telcontar:~ # Ie, there is no "SuSEfirewall2" init script, it is something else that "emulates it". And SuSEfirewall2 is not in the list of packages posted by Ludwig Nussel. Other packages, like "postfix", which is on the list, do have a real init script, at least in 13.1, and also a service file. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)