This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

requesting the return of the syslog daemon


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]