https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |jeffm@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c2 --- Comment #2 from Jeff Mahoney <jeffm@suse.com> 2012-05-01 11:27:35 EDT --- The chkconfig issuse is because the AppArmor init script is called boot.apparmor. sled1:~ # chkconfig boot.apparmor boot.apparmor on AppArmor can be disabled in Yast in Expert Mode but doesn't come up in the regular interface because it's a boot level service. None of the boot level services are display in the "Simple Mode" yast runlevel editor. I'm not sure what to do about the boot.apparmor inconsistency. On one hand, there seems to be a convention to naming boot-level service files with a boot prefix. On the other hand, it's the only boot-level service to have a matching /sbin/rc* script. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c4 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #4 from Christian Boltz <suse-beta@cboltz.de> 2012-08-10 14:19:28 CEST --- (In reply to comment #1)

When I try to disable AppArmor in the Yast2 GUI or the Yast2 ncurses interface, nothing happens.

That might be a bug in YaST. Please open a separate bugreport for YaST and attach the y2logs. Please also add me to CC. (In reply to comment #2)

sled1:~ # chkconfig boot.apparmor boot.apparmor on

Exactly - that's what you need to use on 12.1 and 12.2.

I'm not sure what to do about the boot.apparmor inconsistency. On one hand, there seems to be a convention to naming boot-level service files with a boot prefix. On the other hand, it's the only boot-level service to have a matching /sbin/rc* script.

Indeed, it's an interesting[tm] question. I tend to keep the boot.apparmor name - sometimes it's better to keep a slightly inconsistent, but well-known name than to "fix" it (needless to say that handling the renaming on upgrades will be funny[tm]) and confuse long-time users ;-) BTW: With systemd, you don't need the "boot." prefix to start, reload etc. AppArmor: # systemctl reload apparmor.service Interestingly, for systemctl enable/disable, you still need the prefix: # systemctl disable apparmor.service Failed to issue method call: No such file or directory # systemctl enable boot.apparmor.service boot.apparmor.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig boot.apparmor on Frederic, what's the reason for this (IMHO) inconsistent behaviour? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c6 --- Comment #6 from Jeff Mahoney <jeffm@suse.com> 2012-08-10 09:36:18 EDT --- Christian, it's not a YaST bug, it's by design. Services that match boot.* are only available in expert mode. The only way to make the service available to chkconfig and yast non-expert mode is to rename the script to just 'apparmor.' Incidentally, the scripts on other distros *are* just named 'apparmor.' -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c8 --- Comment #8 from Jeff Mahoney <jeffm@suse.com> 2012-08-10 10:20:30 EDT --- Hehe ok, the only one on my workstation. ;) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c10 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #10 from Frederic Crozat <fcrozat@suse.com> 2012-08-23 11:38:04 UTC --- (In reply to comment #9)

(In reply to comment #5)

...

I think this inconsistency is coming from the fact enabling / disabling non systemd services (ie initscripts) is deletaged to chkconfig. [...]

Maybe we could improve this behaviour for enable / disable (hoping there isn't services providing a boot.foobar and foobar initscripts otherwise it won't be possible to discriminate them)

Given the fact that they can^Wmust be started/stopped/reloaded without the "boot." prefix (where you could have the same name conflicts), I'd say it makes sense to do the same for enable and disable ;-)

Do you want a separate bugreport/enhancement request for systemd?

I've fixed this in systemd for 12.2 (currently in home:fcrozat:branches:Base:System/systemd, should land soon in Base:System and 12.2) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c12 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #12 from Christian Boltz <suse-beta@cboltz.de> 2013-01-06 12:57:22 CET --- The correct resolution for this bug would be 50% FIXED and 50% WONTFIX ;-) 50% FIXED because "systemctl enable apparmor.service" and "systemctl disable apparmor.service" now work (see comment #11). 50% WONTFIX because chkconfig still requires "boot.apparmor". The reasons for WONTFIX are: - it worked this way since ever AFAIK, so changing it would confuse users - the problem will go away when AppArmor comes with a native systemd .service file (which I'll probably add after the 12.3 release) -- 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.