On 2015/01/20 10:04, Theo de Raadt wrote: > > The one I remember was a mechanism to give the name of an rc.d script from > > packages to use in place of a base daemon. Too confusing and complicated, > > local changes to /etc/rc seemed a better idea. > > I do not see the need for replacing syslogd because > > a) Alexander Bluhm is currently adding most of the features people miss, > properly, in a modern fashion > > b) For local reception, syslogd is a tightly coupled system service > i) using sendsyslog(2) > ii) jailed / stack protector failures are logged without times > and syslogd understands this > iii) started as early as possible to remember the boot story > > c) For syslog protocol proxying, syslogd can hand off to a seperate daemon > doing tricky remote delivery services we don't do yet
And of course this "remote" delivery can be "to another syslog running on the same machine", which is the way I'd recommend running on OpenBSD if you have a requirement to use some other syslogd. (If you don't want to log to disk twice, you could just use memory buffers.) > d) Complaints about other daemons come very rarely, indicating there > is no serious development support. Providing the ability in /etc/rc > is like handing children guns. >
