Bug 114322 - Can not disable AppArmor
Summary: Can not disable AppArmor
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: AppArmor (show other bugs)
Version: Beta 3
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Jesse Michael
QA Contact: Keiran Haggerty
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 04:15 UTC by Magnus Boman
Modified: 2005-09-09 08:13 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Boman 2005-08-31 04:15:34 UTC
I enabled AppArmor to have a quick look, but noticed that I couldn't start GAIM
with it enabled. So I went in and disabled it. GAIM could now start. But after a
restart of my box, AppArmor enables itself again. Can't seem to permanently
disable it.
I used YaST to enable AppArmor. Also used YaST to try to disable it.
Comment 1 Dominic W Reynolds 2005-08-31 05:06:49 UTC
Jesse: can you look at this on beta3?
Comment 2 Jana Jaeger 2005-08-31 07:23:54 UTC
just a comment: restarting the box starts things as they are configured 
runlevel-wise. To disable AppArmor permanently it has to be removed from the 
respective runlevels. Otherwise it will automatically get restarted every time a 
user boots his machine.

To permanently disable a service, a user can start the YaST runlevel editor and 
disable the service there. This way, he would have to explicitely enable it with 
this tool again, if he ever wants to use it again.
Comment 3 Jana Jaeger 2005-08-31 15:49:33 UTC
mention this in the docs? Maybe in the troubleshooting section? 
Comment 4 Jesse Michael 2005-09-09 08:13:17 UTC
this is fixed now.  the apparmor control panel in yast was only starting and
stopping the init script.  i've changed it to use insserv to enable and disable
subdomain as well.