[syslog-ng] Re: bug?

[Balazs Scheidler]

Hi,

Thanks for reporting this. I am going to fix these as soon as I'll have some
time.

On Wed, Jul 14, 1999 at 10:15:06AM -0700, joeym@inficad.com wrote:
> Sorry to bother you again, but I have noticed some strange behavior when
> logging over TCP.
> 
> Client Machine is BSDI 4.0 running syslog-ng.  'Server' machine is
> FreeBSD 3.2-STABLE running syslog-ng and receiving UDP, TCP, and local
> syslog msgs.  When the client machine sends messages via UDP back to the
> server machine, the server machine sees the tag as the correct hostname.
> When the messages are sent from the client -> server via TCP, then the
> server marks those messages as coming from its own hostname, and not the
> client's hostname.
> 
> Also, I noticed that sending SIGHUP to syslog-ng on the BSDI client
> machine causes this message (in debug mode) to be sent :
> new configuration initialized
> io_iter(): no waiting fds and no callouts! exiting...
> 
> and then it exits..  If i SIGHUP syslog-ng on the 'server' machine, it
> reloads its config and moves happily on.

-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
     url: http://www.balabit.hu/pgpkey.txt