The syslog-ng logger has (build-optional) support for capabilities. If capabilities support is enabled, running it without setcap/getcap permissions gives the following upon start: * Starting syslog-ng ... syslog-ng: Error setting capabilities, capability management disabled; error='Permission denied' [ ok ] Granting only setcap (initial AVC seen) does not fully help either: * Starting syslog-ng ... Error managing capability set, cap_set_proc returned an error; With setcap and getcap enabled, syslog-ng starts and functions fine. See also https://bugs.gentoo.org/show_bug.cgi?id=488718 Reported-by: Vincent Brillault <gentoo@lerya.net> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be> |
||
---|---|---|
.. | ||
flask | ||
modules | ||
support | ||
constraints | ||
global_booleans | ||
global_tunables | ||
mcs | ||
mls | ||
policy_capabilities | ||
users |