From 7452f34279f29a1d7a302e0809c23f8eeac92afe Mon Sep 17 00:00:00 2001
From: Christian Boltz <apparmor@cboltz.de>
Date: Sun, 3 Mar 2024 18:18:12 +0100
Subject: [PATCH] Update ancient paths in apparmor and apparmor.d manpage

- replace example calls of /etc/init.d/apparmor with apparmor.service
- drop /etc/init.d/apparmor in filelist
- replace /var/lib/apparmor/ with /var/cache/apparmor/
---
 parser/apparmor.d.pod |  2 --
 parser/apparmor.pod   | 13 +++++--------
 2 files changed, 5 insertions(+), 10 deletions(-)

diff --git a/parser/apparmor.d.pod b/parser/apparmor.d.pod
index 96f794695..bdd7dec8a 100644
--- a/parser/apparmor.d.pod
+++ b/parser/apparmor.d.pod
@@ -2037,8 +2037,6 @@ An example AppArmor profile:
 
 =over 4
 
-=item F</etc/init.d/boot.apparmor>
-
 =item F</etc/apparmor.d/>
 
 =back
diff --git a/parser/apparmor.pod b/parser/apparmor.pod
index 95c10d09d..2585e5c0c 100644
--- a/parser/apparmor.pod
+++ b/parser/apparmor.pod
@@ -36,12 +36,11 @@ of resources. AppArmor's unique security model is to bind access control
 attributes to programs rather than to users.
 
 AppArmor confinement is provided via I<profiles> loaded into the kernel
-via apparmor_parser(8), typically through the F</etc/init.d/apparmor>
-SysV initscript, which is used like this:
+via apparmor_parser(8), typically through the F<apparmor.service>
+systemd unit, which is used like this:
 
-	# /etc/init.d/apparmor start
-	# /etc/init.d/apparmor stop
-	# /etc/init.d/apparmor restart
+	# systemctl start apparmor
+	# systemctl reload apparmor
 
 AppArmor can operate in two modes: I<enforcement>, and I<complain or learning>:
 
@@ -273,11 +272,9 @@ Else, if auditd is running, see auditd(8) and auditd.conf(5).
 
 =over 4
 
-=item F</etc/init.d/apparmor>
-
 =item F</etc/apparmor.d/>
 
-=item F</var/lib/apparmor/>
+=item F</var/cache/apparmor/>
 
 =item F</var/log/audit/audit.log>