This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/963] syslog() does not always NL terminate messages
- From: "drepper at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 27 Sep 2005 15:20:22 -0000
- Subject: [Bug libc/963] syslog() does not always NL terminate messages
- References: <20050523154812.963.bazsi@balabit.hu>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From drepper at redhat dot com 2005-09-27 15:20 -------
> The problem is that sometimes neither NL or NUL is present. For example,
> here is an strace dump of syslog-ng, reading sendmail logs, which is using
> the syslog functions from libc:
I cannot see how this could happen if the programs really use the libc syslog.
We always send the NUL byte if the syslog socket is connected to a TCP server.
Provide a test case.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
http://sourceware.org/bugzilla/show_bug.cgi?id=963
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.