On Wed, Dec 18, 2002 at 07:38:54PM -0500, Mikhail Teterin wrote:
>Although removing the syslogd seems natural, since the syslog(3) send
>the info directly to EventLog, it is wrong.
We didn't "remove" syslogd. It never existed.
Requests sent to the ether for someone to do something for you rarely
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 t
2 matches
Mail list logo