Bug#2881: syslogd doesn't treat pipes correctly
You (Ian Jackson) wrote:
> If I could explain in a little more detail what I think the desirable
> behaviour would be:
> I'd like syslog to try to open the pipe for writing, or perhaps for
> both at once, and to discard output while there are no readers (eg, by
> catching or ignoring SIGPIPE and by ignoring EPIPE).
You can do a select() before trying to write() to see if there are
any readers present. Oh and you _do_ have to open the fifo O_RDWR with
newer kernels. (Same problem as with sysvinit < 2.60)
Miquel van | Cistron Internet Services -- Alphen aan den Rijn.
Smoorenburg, | mailto:firstname.lastname@example.org http://www.cistron.nl/
email@example.com | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)