This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.7.0-67: syslog() not working properly - possible bug in writev() ?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 2 Dec 2009 11:04:33 +0100
- Subject: Re: 1.7.0-67: syslog() not working properly - possible bug in writev() ?
- References: <1NFlZ1-0LCxsG0@fwd11.aul.t-online.de>
- Reply-to: cygwin at cygwin dot com
On Dec 2 10:31, Christian Franke wrote:
> syslog() produces bogus lines in /var/log/messages.
>
> Testcase (with syslog-ng):
>
> $ echo -e 'one\ntwo\nthree' | logger -t test
>
> $ tail /var/log/messages
> ...
> Dec 2 10:12:31 localhost kernel:
> Dec 2 10:12:31 localhost test: one
> Dec 2 10:12:31 localhost kernel:
> Dec 2 10:12:31 localhost test: two
> Dec 2 10:12:31 localhost kernel:
> Dec 2 10:12:31 localhost test: three
>
> I presume that the root of the problem is that the
>
> writev(fd, { {"<PRI style="margin:0px;">", . }, { "MSG", . } }, 2)
>
> used within syslog() sends "<PRI style="margin:0px;">" and "MSG" in two
> separate datagrams to /dev/log.
Probably not. The "kernel:" message is generated if something is
available on /dev/kmsg, which shouldn't be the case. The only message
type generated there are exceptions catched by Cygwin. I'll have a look
into it. Thanks for the report.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple