29 Jan
2007
29 Jan
'07
12:18 p.m.
Hari Sekhon (hpsekhon@googlemail.com) wrote on 29 January 2007 12:13:
Have you tried adding the syslog-ng user to a group and granting permissions on /dev/log or whatever you have to that group such
chown root:logger /dev/log
ls -l /dev/log srw-rw-rw- 1 root logger 0 Jan 27 03:10 /dev/log=
Then restart syslog-ng and it should be able to read from the socket.
That shouldn't be necessary because it opens /dev/log before dropping root privileges. Also, messages to auth log are recorded, even though to kernel log are not.