On 10 April 2014 02:24, Carlos E. R. <robin.listas@telefonica.net> wrote:
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.
I mentioned SuSEfirewall because of my recent experience looking into Bug 869386 where multiple methods of running SuSEfirewall caused much confusion and problem https://bugzilla.novell.com/show_bug.cgi?id=869386 So the scenario was fresh in my mind, even if not 100% accurate for this discussion, I still think it's illustrative of why we only should have 1 way of starting/stopping a service (with other methods, eg. rc$foo, being aliases) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org