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 From: Mikhail Teterin Message-Id: <200212190038.gBJ0csc7027747@corbulon.video-collage.com> Subject: requesting the return of the syslog daemon To: cygwin AT cygwin DOT com Date: Wed, 18 Dec 2002 19:38:54 -0500 (EST) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Scanned-By: MIMEDefang 2.21 (www . roaringpenguin . com / mimedefang) Although removing the syslogd seems natural, since the syslog(3) send the info directly to EventLog, it is wrong. The syslog(3) should try to send to the local syslogd (at least, once per program's life-time). Failing that, it can send to EventLog -- as it currently does. Then, the decision, as to what to do with the messages can be returned to the administrator, with EventLog being just one of the possible options (perhaps, a default one) configurable through the good old /etc/syslog.conf. Something like this should be possible: local6.* @loghost *.* |EventLog Yours, -mi -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/