Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 30 Jun 2005 22:08:59 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Syslog-ng Message-ID: <20050630200859.GH21074@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=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jun 30 15:19, Tony Karakashian wrote: > I've seen lots of people who got syslog-ng working on their cygwin > boxes. Latest version compiles just fine out of the box, but not sure > what I should put in for a source in the syslog-ng.conf? Default for > Linux is to use /proc/kmesg, but we don't have one under Cygwin. Are > Cygwin installs limited to remote clients only? Dunno what you're up to but I'm running syslog from inetutils just fine. Cygwin tries to syslog on /dev/log if it's available (it's usually created by syslog) and there's also a /dev/kmsg pipe which would be utilized for kernel messages ... *if* Cygwin would have anything like kernel messages. Nothing gets sent to /dev/kmsg so far. Right now it's's only a proof of concept for using mailslots. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/