765e7b71ee
Since most distributions now support /run (which, thanks the the file context substitutions, is marked as var_run_t), we need to update the SELinux policies to support "dynamically" building up /run. Unlike /var/run, which is most likely statically defined during distribution installation, /run is a tmpfs which is built up from scratch on each and every boot. But not only that, many services also use this location for other purposes than just PID files (which is to be expected as these "other reasons" is why /run came to be in the first place), so we need to support other types within this location easily. For this reason, we introduce support to - creating the /run/lock location - supporting named file transitions when init scripts create stuff in /run Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be> |
||
|---|---|---|
| .. | ||
| admin | ||
| apps | ||
| contrib@88fcbee475 | ||
| kernel | ||
| roles | ||
| services | ||
| system | ||