X-Spam-Check-By: sourceware.org Date: Sat, 31 Dec 2005 15:17:33 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: syslog LOG_PERROR option and newline Message-ID: <20051231141733.GI32312@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <8389af8b0512310538m29b3a3dayb0832be3806bfd9e AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8389af8b0512310538m29b3a3dayb0832be3806bfd9e@mail.gmail.com> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 31 22:38, Hiroki Sakagami wrote: > When I use LOG_PERROR option on openlog() call, syslog() does not > append a newline to the log message. Is this an intentional behavior? It's a bug. I've fixed it in CVS. Thanks for the report, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/