On Mon, 2017-07-31 at 16:30 +0000, Tyler Hicks wrote: > Make the possible exit status values bold to match the style used in > aa-status.pod as of r3680. > > Signed-off-by: Tyler Hicks <[email protected]>
Acked-By: Jamie Strandboge <[email protected]> > --- > binutils/aa-enabled.pod | 12 ++++++------ > 1 file changed, 6 insertions(+), 6 deletions(-) > > diff --git a/binutils/aa-enabled.pod b/binutils/aa-enabled.pod > index bc9603e..5eef9de 100644 > --- a/binutils/aa-enabled.pod > +++ b/binutils/aa-enabled.pod > @@ -56,27 +56,27 @@ Upon exiting, B<aa-enabled> will set its exit status to > the following values: > > =over 4 > > -=item 0: > +=item B<0> > > if AppArmor is enabled. > > -=item 1: > +=item B<1> > > if AppArmor is not enabled/loaded. > > -=item 2: > +=item B<2> > > intentionally not used as an B<aa-enabled> exit status. > > -=item 3: > +=item B<3> > > if the AppArmor control files aren't available under /sys/kernel/security/. > > -=item 4: > +=item B<4> > > if B<aa-enabled> doesn't have enough privileges to read the apparmor control > files. > > -=item 64: > +=item B<64> > > if any unexpected error or condition is encountered. > -- Jamie Strandboge | http://www.canonical.com
signature.asc
Description: This is a digitally signed message part
-- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
