Hi! On Fri, 2006-09-22 at 20:33 +0200, Marco d'Itri wrote: > reopen 384802 > thanks > > On Sep 22, SZALAY Attila <[EMAIL PROTECTED]> wrote: > > Not exactly. > > If you use only the syslog(3) function, you are right, but if you open a > > connection to syslog with openlog(3) in the begining of your application > > then you will be in trouble when syslog-ng listen in unix-dgram and have > > been reloaded. At least with the version 1.6.X of syslog-ng. > No. As you can verify using the attached program, the same system calls > are used no matter if you use openlog(3) or not.
Yes, but in libc6 set a global variable when openlog called. (The fd to /dev/log) > > It's possible that in version 2.0 the syslog-ng could keep unix-dgram > > connections between reload, but I'm too conservative to change it. (If > There are no connections, datagram sockets are connectionless. Yes, there are. In normal way (tcp/ip) that connection is virtual, but in unix type socket there are no such type of connectionless socket. > > you read the Changelog you could recognize the time when I > > changes /dev/log from unix-stream to unix-dgram. And the funny thins > > _is_ that because of this change I have to restart every daemon which > > send log messages. Because the running daemons couldn't recognize that > > unix-dgram /dev/log is no more. > Looks like your troubles were unrelated. > It can be easily verified using the attached test program, which creates > a datagram socket, that when the syslog daemon is restarted while it is > running the socket is reopened: I don't think so, just the libc6 is upgraded after that time. > This does not justify closing the bug. Hmm. I don't want to close the bug. Anyway. What is the advantage of unix-dgram against unix-stream for you? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
