From: Mike van der Velden (mvanderv@redback.com)
Date: Fri Jun 03 2005 - 20:33:28 EDT
Greetings,
We develop a turnkey application that runs on Solaris 9, on small to
midrange Sun servers (eg. 240s, 480s).
Recently, our developers noted that syslog's streams interface behaves
differently than its datagram interface.
We are running into unusual behaviour with the syslog daemon in Solaris 9.
If we send the syslog daemon a message like: "some text\nsome more
text" and we sent it to the UDP port 514 then the syslog daemon stores
the log message as a single line.
If we send syslog the same message but use domain sockets then the
syslog daemon stores the log message as 2 lines.
We're interested in finding out if we can configure syslog so we get
the same behaviour when we send the message to the UDP port 514.
I've looked for syslogd patches, but the patches that are available do
not address this issue. I've googled, and it does appear to be a
problem that has been around for a while.
Basically, if we send messages using domain sockets, the message gets
treated properly. But over UDP, the message headers are treated
differently, the \n are replaced by spaces, and a few other things, I am
told.
Has anyone else come across this?
I have suggested that they try syslog-ng, but I am told they really
don't want to add an additional 3rd party packages to our existing
distribution. So, fixes to the existing syslog are preferred.
Thanks in advance, and I *always* summarize!
-- Mike van der Velden email mvanderv@redback.com Professional Services voice 604-629-7327 Redback Networks Canada, Inc. cell 604-868-1562 200 - 4190 Still Creek Drive fax 604-294-8830 Burnaby, BC. Canada V5C 6C6 _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:49 EDT