X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 2 Dec 2009 11:04:33 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.0-67: syslog() not working properly - possible bug in  writev()  ?
Message-ID: <20091202100433.GQ8059@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1NFlZ1-0LCxsG0 AT fwd11 DOT aul DOT t-online DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1NFlZ1-0LCxsG0@fwd11.aul.t-online.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list 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