|
Bugzilla – Full Text Bug Listing |
| Summary: | Can not disable AppArmor | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Magnus Boman <mboman> |
| Component: | AppArmor | Assignee: | Jesse Michael <jmichael> |
| Status: | RESOLVED FIXED | QA Contact: | Keiran Haggerty <khaggerty> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Magnus Boman
2005-08-31 04:15:34 UTC
Jesse: can you look at this on beta3? 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. mention this in the docs? Maybe in the troubleshooting section? 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. |