Currently, the files_manage_generic_locks only handles the lock files. If a domain needs to manage both lock files and the lock directories (like specific subdirectories in /var/lock that are not owned by a single other domain, such as Gentoo's /var/lock/subsys location) it also needs the manage permissions on the directory. This is to support OpenRC's migration of /var/lock to /run/lock which otherwise fails: * Migrating /var/lock to /run/lock cp: cannot create directory '/run/lock/subsys': Permission denied rm: cannot remove '/var/lock/subsys': Permission denied Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be> |
||
---|---|---|
.. | ||
flask | ||
modules | ||
support | ||
constraints | ||
global_booleans | ||
global_tunables | ||
mcs | ||
mls | ||
policy_capabilities | ||
users |