[apparmor] [PATCH 2/2] utils: update aa-status.pod to unify exit status and bugs sections

Tyler Hicks tyhicks at canonical.com
Mon Jul 31 16:30:16 UTC 2017


Create an EXIT STATUS header and place the BUGS section after the EXIT
STATUS section to match the style in aa-enabled.pod.

Signed-off-by: Tyler Hicks <tyhicks at canonical.com>
---
 utils/aa-status.pod | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/utils/aa-status.pod b/utils/aa-status.pod
index 22f9868..677f89b 100644
--- a/utils/aa-status.pod
+++ b/utils/aa-status.pod
@@ -91,13 +91,9 @@ displays a short usage statement.
 
 =back
 
-=head1 BUGS
-
-B<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.
+=head1 EXIT STATUS
 
-Upon exiting, B<aa-status> will set its return value to the
+Upon exiting, B<aa-status> will set its exit status to the
 following values:
 
 =over 4
@@ -125,6 +121,12 @@ the apparmor control files.
 
 =back
 
+=head1 BUGS
+
+B<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.
+
 If you find any additional bugs, please report them at
 L<https://bugs.launchpad.net/apparmor/+filebug>.
 
-- 
2.7.4




More information about the AppArmor mailing list