Novell LINUX ENTERPRISE SERVER 10 - INSTALLATION AND ADMINISTRATION 04-08-2006 Installation Manual page 885

Test your profile settings by performing every task you need with the application you
just confined. Normally, the confined program runs smoothly and you do not notice
AppArmor activities at all. However, if you notice certain misbehavior with your appli-
cation, check the system logs and see if AppArmor is too closely constricting your ap-
plication. Depending on the log mechanism used on your system, there are several
places to look for AppArmor log entries:
/var/log/audit.log
If the audit package is installed and auditd is running, AppArmor events are
logged as follows:
type=APPARMOR msg=audit(1140325305.502:1407): REJECTING w access to
/usr/lib/firefox/update.test (firefox-bin(9469) profile
/usr/lib/firefox/firefox-bin active /usr/lib/firefox/firefox-bin)
/var/log/messages
If auditd is not used, AppArmor events are logged in the standard system log under
/var/log/messages. An example entry would look like the following:
Feb 22 18:29:14 dhcp-81 klogd: audit(1140661749.146:3): REJECTING w access
to /dev/console (mdnsd(3239) profile /usr/sbin/mdnsd active
/usr/sbin/mdnsd)
dmesg
If auditd is not running, AppArmor events can also be checked using the dmesg
command:
audit(1140661749.146:3): REJECTING w access to /dev/console (mdnsd(3239)
profile /usr/sbin/mdnsd active /usr/sbin/mdnsd)
To adjust the profile, analyze the log messages relating this application again as described
in Step 3 (page 884). Determine the access rights or restrictions when prompted.
TIP: For More Information
For more information about profile building and modification, refer to Chap-
ter 3, Building Novell AppArmor Profiles (↑Novell AppArmor 2.0 Administration
Guide).
Confining Privileges with AppArmor 885