Dear Kees, I found myself in a pretty interesting case of "killing two birds with one rock" with a very very little change that could solve this and provide a nice feature in the same way.
I was taking a look at this code snip:
# Reload the profile, including any abstraction updates
if type aa-status >/dev/null && aa-status --enabled 2>/dev/null; then
apparmor_parser -r -T -W "$APP_PROFILE" || true
fi
I ended up realizing that if it wasn't because of this "if type
aa-status >/dev/null" and it's consequent error[1], I would be able to
set apparmor into a suggested list, instead of a strong dependency.
What do you think about switching "if type aa-status" for a "if [ -x
/usr/sbin/aa-status ]" instead?
Thanks in advance.
:d:
ref.
1. type aa-status thrown errors are not redirected to /dev/null, showing
a harmless /but still present/ error message to the user (checkout
etc/init.d/kymap.sh or etc/init.d/cups)
--
BOFH excuse #280:
Traceroute says that there is a routing problem in the backbone. It's not our
problem.
signature.asc
Description: OpenPGP digital signature
