On 2014-07-14, Theo de Raadt <dera...@cvs.openbsd.org> wrote:

> CVSROOT:      /cvs
> Module name:  src
> Changes by:   dera...@cvs.openbsd.org 2014/07/13 22:02:33
>
> Modified files:
>       usr.sbin/syslogd: syslogd.c 
>
> Log message:
> Create a socketpair() and tie one end to /dev/klog using ioctl LIOCSFD.
> This allows us to receive messages direct from programs using the
> fd-safe sendsyslog(2), aka. syslog_r(3).  Thanks to guenther for this part
> of the solution.
> ok beck tedu miod guenther

Theo has reminded me that any syslogd replacements we may have in
ports, e.g. sysutils/rsyslog, will require a corresponding change
or they will NOT work as a drop-in replacement.

Should we mark all candidates we can find as BROKEN to prevent
surprises?

-- 
Christian "naddy" Weisgerber                          na...@mips.inka.de

Reply via email to