https://bugs.exim.org/show_bug.cgi?id=2982
--- Comment #3 from Martin Kealey <from-exim-bugzi...@kurahaupo.gen.nz> --- "syslog over UDP is unreliable" is one of those things that while technically true, us rarely a real problem. Loss of UDP packets is caused by two factors: the underlying transport dropping oackets, and the receiver's packet queue (in the kernel) overrunning. Sending between containers within one host has 100% reliable transport - otherwise you have a kernel bug - and the only things that could stall syslogd enough to cause overruns would be IO bandwidth saturation and delayed process scheduling, both of which are manageable. The log messages are a tiny fraction of the size of the messages that are being transported, so in practice this risk is tolerable for many. If your use case cannot tolerate even a one-in-a-million loss of log messages, then you would want to use the syslog-to-stdout module that I posted before. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
