Comment 4 for bug 1878333

Revision history for this message
Daniel Richard G. (skunk) wrote :

Thanks. I am in complete agreement.

I don't need (or even want) AppArmor to automagically update the kernel state right after changing something under /etc/apparmor.d/, because having to do a SIGHUP/restart/etc. is already normal practice. But I do expect that a reboot/reload will take care of that for me, as it does for other services.