Environment
Novell Open Enterprise Server 2 (OES 2) Linux
Situation
Resolution
There are a lot of ways to disable an application.
Here is a way directly from the documentation to disable AppArmor:
19.2 Enabling and Disabling AppArmor
AppArmor is configured to run by default on any fresh installation of SUSE Linux Enterprise Desktop. There are two ways of toggling the status of AppArmor:
- Using YaST System Services (Runlevel)
-
Disable or enable AppArmor by removing or adding its boot script to the sequence of scripts executed on system boot. Status changes are applied on reboot.
- Using AppArmor Control Panel
-
Toggle the status of AppArmor in a running system by switching it off or on using the YaST AppArmor Control Panel. Changes made here are applied instantaneously. The Control Panel triggers a stop or start event for AppArmor and removes or adds its boot script in the system's boot sequence.
To disable AppArmor permanently (by removing it from the sequence of scripts executed on system boot) proceed as follows:
-
Start YaST.
-
Select
. -
Select
. -
Select boot.apparmor and click .
-
Exit the YaST Runlevel tool with
.
AppArmor will not be initialized on reboot, and stays inactive until you reenable it. Reenabling a service using the YaST Runlevel tool is similar to disabling it.
Toggle the status of AppArmor in a running system by using the AppArmor Control Panel. These changes take effect as soon as you apply them and survive a reboot of the system. To toggle AppArmor's status, proceed as follows:
-
Start YaST.
-
Select
. -
Select
. To disable AppArmor, uncheck this option. -
Exit the AppArmor Control Panel with
.
You might want to disable it manually like this:
List information about how it is configured to be run currently:
chkconfig -A | grep -i app
Stop it from loading on boot like this:
chkconfig boot.apparmor off
Stop it from running right now like this:
/etc/init.d/boot.apparmor stop
Rerun the OES install for AFP and it will now install without this error.