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.