aa_find_mountpoint(2) [debian man page]
AA_FIND_MOUNTPOINT(2) AppArmor AA_FIND_MOUNTPOINT(2) NAME
aa_is_enabled - determine if apparmor is available aa_find_mountpoint - find where the apparmor interface filesystem is mounted SYNOPSIS
#include <sys/apparmor.h> int aa_is_enabled(void); int aa_find_mountpoint(char **mnt); Link with -lapparmor when compiling. DESCRIPTION
The aa_is_enabled function returns true (1) if apparmor is enabled. If it isn't it sets the errno(3) to reflect the reason it is not enabled and returns 0. The aa_find_mountpoint function finds where the apparmor filesystem is mounted on the system, and returns a string containing the mount path. It is the caller's responsibility to free(3) the returned path. RETURN VALUE
aa_is_enabled On success 1 is returned. On error, 0 is returned, and errno(3) is set appropriately. aa_find_mountpoint On success zero is returned. On error, -1 is returned, and errno(3) is set appropriately. ERRORS
aa_is_enabled ENOSYS AppArmor extensions to the system are not available. ECANCELED AppArmor is available on the system but has been disabled at boot. ENOENT AppArmor is available (and maybe even enforcing policy) but the interface is not available. ENOMEM Insufficient memory was available. EPERM Did not have sufficient permissions to determine if AppArmor is enabled. EACCES Did not have sufficient permissions to determine if AppArmor is enabled. aa_find_mountpoint ENOMEM Insufficient memory was available. EACCES Access to the required paths was denied. ENOENT The apparmor filesystem mount could not be found BUGS
None known. If you find any, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>. SEE ALSO
apparmor(7), apparmor.d(5), apparmor_parser(8), and <http://wiki.apparmor.net>. AppArmor 2.7.103 2012-06-28 AA_FIND_MOUNTPOINT(2)
Check Out this Related Man Page
AA-STATUS(8) AppArmor AA-STATUS(8) NAME
aa-status - display various information about the current AppArmor policy. SYNOPSIS
aa-status [option] DESCRIPTION
aa-status will report various aspects of the current state of AppArmor confinement. By default, it displays the same information as if the --verbose argument were given. A sample of what this looks like is: apparmor module is loaded. 110 profiles are loaded. 102 profiles are in enforce mode. 8 profiles are in complain mode. Out of 129 processes running: 13 processes have profiles defined. 8 processes have profiles in enforce mode. 5 processes have profiles in complain mode. Other argument options are provided to report individual aspects, to support being used in scripts. OPTIONS
aa-status accepts only one argument at a time out of: --enabled returns error code if AppArmor is not enabled. --profiled displays the number of loaded AppArmor policies. --enforced displays the number of loaded enforcing AppArmor policies. --complaining displays the number of loaded non-enforcing AppArmor policies. --verbose displays multiple data points about loaded AppArmor policy set (the default action if no arguments are given). --help displays a short usage statement. BUGS
aa-status must be run as root to read the state of the loaded policy from the apparmor module. It uses the /proc filesystem to determine which processes are confined and so is susceptible to race conditions. Upon exiting, aa-status will set its return value to the following values: 0 if apparmor is enabled and policy is loaded. 1 if apparmor is not enabled/loaded. 2 if apparmor is enabled but no policy is loaded. 3 if the apparmor control files aren't available under /sys/kernel/security/. 4 if the user running the script doesn't have enough privileges to read the apparmor control files. If you find any additional bugs, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>. SEE ALSO
apparmor(7), apparmor.d(5), and <http://wiki.apparmor.net>. AppArmor 2.7.0~beta1 2010-12-20 AA-STATUS(8)