[syslog-ng] Syslog-ng losing messages on solaris 10

[AndyH at nominet.org.uk]

Hi,

I've been running 2.0.6 on Solaris 10 and it all seemed to be working fine.
On a new application I have found that it loses messages.  This application
sends 3-7000 messages/sec.  Part of these messages contains a unique ID
which increments.

When I run the syslogd as supplied with Solaris 10 then all messages get
logged, but when I use syslog-ng then it loses messages.  On a Sun V210 I
see these messages

message overflow on /dev/log minor #6 -- is syslogd(1M) running?
message overflow on /dev/log minor #6 -- is syslogd(1M) running?
message overflow on /dev/log minor #6 -- is syslogd(1M) running?

on the console, and eventually there is a hardware reset and the server
reboots.

I have tried running syslogd to just pass messages on to syslog-ng and this
doesn't cause the hardware reset, but still loses some messages.  I have
also tried the time_sleep and log_fetch_limit options with no success.

I have noticed that syslogd is multi-threaded but syslog-ng is only single
threaded.  Is this what is causing these messages to get missed?  Are there
any plans for a threaded version?

Anyone have any ideas as to how to get all messages logged with syslog-ng?

Regards
Andy