3 ms·
Any program that uses the syslog(3) library function will also have this problem, as it also blocks (internally it writes to the /dev/log socket file). If the
by otterley 11y ago
Any program that uses the syslog(3) library function will also have this problem, as it also blocks (internally it writes to the /dev/log socket file). If the consumer can't keep up, whether it be rsyslogd or syslog-ng or whatever is listening to the socket, the producer can block as well.
So this is not a new problem. If you really want your producer to drop logs in the event of backpressure, you can directly use the syslog protocol over UDP, but it has tradeoffs too.
- falcolas 11y agoThat depends on the syslogd implementation, and will not cause programs to crash due to disconnected stderr/stdout buffers. Perhaps more importantly, you can swap out the syslogd if you don't like its implementation. This is harder to do (if even possible) with journald.
- otterley 11y agoHave you seen any syslog server implementations that are significantly more performant than journald?