[Bug 746506] New: Apparmor service unknown
https://bugzilla.novell.com/show_bug.cgi?id=746506 https://bugzilla.novell.com/show_bug.cgi?id=746506#c0 Summary: Apparmor service unknown Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: VMWare OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: carlos.e.r@opensuse.org QAContact: qa@suse.de Found By: --- Blocker: --- Apparmor service unknown systemv: Elanor:~ # chkconfig apparmor apparmor: unknown service Elanor:~ # rcapparmor Usage: /sbin/rcapparmor {start|stop|restart|try-restart|reload|force-reload|status|kill} Elanor:~ # systemv: Elanor:~ # chkconfig apparmor apparmor: unknown service Elanor:~ # Yast services configuration also does not displays an entry for AA. -- 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#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c1
Neven Lovrić
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c2
--- Comment #2 from Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c3
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c4
Christian Boltz
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#c5
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c6
--- Comment #6 from Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c7
--- Comment #7 from Carlos Robinson
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.
bombadillo:~ # which rccrypto /sbin/rccrypto bombadillo:~ # l /sbin/rccrypto lrwxrwxrwx 1 root root 23 Aug 7 02:43 /sbin/rccrypto -> /etc/init.d/boot.crypto* bombadillo:~ # :-) -- 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
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c9
Christian Boltz
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? -- 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
(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#c11
--- Comment #11 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=746506
https://bugzilla.novell.com/show_bug.cgi?id=746506#c12
Christian Boltz
participants (1)
-
bugzilla_noreply@novell.com