https://bugzilla.novell.com/show_bug.cgi?id=482532
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=482532#c3
Lukas Ocilka changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P4 - Low |P3 - Medium
CC| |locilka@novell.com
AssignedTo|locilka@novell.com |werner@novell.com
Severity|Minor |Normal
--- Comment #3 from Lukas Ocilka 2009-03-17 05:35:10 MST ---
I've reproduced this issue and it seems it caused by insserv that doesn't
handle runlevel 4 (yes, we somehow support it) correctly.
Scripts, and their default-start options:
* SuSEfirewall2_setup
# Default-Start: 3 4 5
* SuSEfirewall2_init
# Default-Start: 3 4 5
According to logs and my testing, Runlevel Editor was calling these commands:
* /sbin/insserv -f /etc/init.d/SuSEfirewall2_init,start=4
* /sbin/insserv -f /etc/init.d/SuSEfirewall2_setup,start=4
..because user manually disabled the service in runlevels 3 and 5 (but not in
runlevel 4 which is not visible in that case - visibility defined in control
file, see FATE #303798).
A workaround to fully disable a service is to click on [Disable] button in
non-expert configuration in Runlevel Editor. Anyway, insserv should disable the
services in all but runlevel 4 which it doesn't and keeps it enabled in all
default runlevels.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.