[syslog-ng]lost logs when using syslog-ng on Linux due to /dev/log reopen

Borsenkow Andrej [email protected]
Tue, 28 May 2002 12:50:04 +0400

I am using syslog-ng on Mandrake (8.2 and post-8.2), glibc-2.2.5.

Unfortunately, it tends to lose logs. As far as I can tell it is related to
the fact that syslog-ng recreates /dev/log on HUP. It means that every
program that has opened syslog connection won't be able to write to /dev/log

The sad thing is, this is _not_ limited to klogd (that has the same problem)
but to every other program (I had very bad case of socks server losing some
info used for accounting :( It happens to every program (daemon) that does
openlog() only once on startup.

Which makes drop in replacement for syslog simply impossible :(