Your message dated Wed, 20 Sep 2006 22:53:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line unix-dgram or unix-stream
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: syslog-ng
Severity: normal
The default syslog-ng.conf contains this comment:
# standard Linux log source (this is the default place for the syslog()
# function to send logs to)
unix-stream("/dev/log");
But it is wrong: as you can easily verify using strace, libc by default
uses datagram sockets (which for the AF_UNIX family are as reliable as
stream sockets):
$ strace -e trace=socket logger test
socket(PF_FILE, SOCK_DGRAM, 0) = 1
$
For this reason, the default configuration should use unix-dgram.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi All!
The main problem with unix-dgram is that syslog-ng cannot keep the
connection between reloads. And there are programs (for example some
part of sendmail) which doesn't connect again. So you loose log messages
from various parts of the system.
Yes, maybe the reason is bad but it's better to use unix-stream than
unix-dgram.
--- End Message ---
