-=== modified file 'parser/rc.apparmor.functions'
---- parser/rc.apparmor.functions 2011-06-01 14:52:35 +0000
-+++ parser/rc.apparmor.functions 2011-07-14 06:56:45 +0000
-@@ -198,6 +198,7 @@
- aa_log_skipped_msg "$profile"
- logger -t "AppArmor(init)" -p daemon.warn "Skipping profile $profile"
- STATUS=2
-+ continue
- elif [ "$skip" -ne 0 ]; then
- continue
- fi
-@@ -206,7 +207,7 @@
- if force_complain "${profile}" ; then
- COMPLAIN="-C"
- fi
-- $PARSER $ABSTRACTIONS $PARSER_ARGS $COMPLAIN "$profile" > /dev/null
-+ $PARSER $ABSTRACTIONS $PARSER_ARGS $PARSER_CUSTOM_ARGS -W $COMPLAIN "$profile" > /dev/null
- if [ $? -ne 0 ]; then
- aa_log_failure_msg "$profile failed to load"
- STATUS=1
-
-=== modified file 'parser/subdomain.conf'
---- parser/subdomain.conf 2011-01-13 21:58:26 +0000
-+++ parser/subdomain.conf 2011-07-14 06:59:27 +0000
-@@ -23,6 +23,11 @@
- # Enable the AppArmor event daemon for reporting?
- APPARMOR_ENABLE_AAEVENTD="no"
+--- apparmor-3.0.1/parser/parser.conf~ 2020-12-02 12:01:37.000000000 +0100
++++ apparmor-3.0.1/parser/parser.conf 2021-02-07 18:55:26.427209119 +0100
+@@ -31,7 +31,7 @@
+ # match-string "pattern=aadfa audit perms=crwxamlk/ user::other"
-+## Path: System/AppArmor
-+## Description: Custom user flags for apparmor profile parser
-+#
-+PARSER_CUSTOM_ARGS=""
-+
- #SUBDOMAIN_MODULE_PANIC=XXX
- #This option controls how subdomain behaves when the init script attempts
- #to load the AppArmor module and fails. There are 4 options
-
+ ## Turn creating/updating of the cache on by default
+-#write-cache
++write-cache
+
+ ## Show cache hits
+ #show-cache