table of contents
other versions
- buster 2.13.2-10
- testing 2.13.6-9
- unstable 2.13.6-10
- experimental 3.0.1-6
AA_FIND_MOUNTPOINT(2) | AppArmor | AA_FIND_MOUNTPOINT(2) |
NAME¶
aa_is_enabled - determine if apparmor is availableaa_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 <https://bugs.launchpad.net/apparmor/+filebug>.SEE ALSO¶
apparmor(7), apparmor.d(5), apparmor_parser(8), and <https://wiki.apparmor.net>.2019-03-30 | AppArmor 2.13.2 |