Anand, Which SELinux policy are you using: targeted or strict? If you are using the targeted policy, check this message: https://lists.balabit.hu/pipermail/syslog-ng/2005-April/007347.html jpo Anand Shankar wrote:
I recently installed syslog-ng successfully on a FC3-SELinux enabled box. Everything is fine except that:
# service syslog-ng status
syslog-ng dead but subsys locked
# ls --context /var/lock/subsys/syslog-ng
-rw------- root root root:object_r:var_lock_t syslog-ng
The root:object_r:var_lock_t should have been user_u:object_r:var_lock_t, and that is what is causing syslog-ng daemon to die. Also, the file permissions generally are 666.
One easy way is to switch off SELinux for syslog-ng, but is there a better way?? Why are the permissions wrong??
-- José Pedro Oliveira * mailto: jpo@di.uminho.pt * http://gsd.di.uminho.pt/~jpo * * gpg fingerprint = F9B6 8D87 859D 1C94 48F0 84C0 9749 9EB5 91BD 851B *