X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 16 Nov 2011 10:09:54 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: how to log "fork errors", cygheap errors with syslogd Message-ID: <20111116090954.GA7335@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Nov 16 08:07, Heiko Elger wrote: > Hello, > > I'm sorry - but cause of sometimes having unpredictable and unreproduceable > cygwin errors like "fork error, cygheap check", I trieded to run syslogd to > log these all these errors in /var/log/messages. > > But these kind of errors are not logged there. > How do I have to configure my syslogd - or is it not possible to log these > kind of errors. No, it's not. The messages are printed using special debug output functions, not the syslog API. 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