Hi William, (apologies for the high volume in this thread)
> haproxy 1.4 and pre 2a4a44f0f9f behavior (expected): > every syslog message ends with \n > > post 2a4a44f0f9f (REORG: log: split send_log function) behavior: > every syslog message ends with \n + 1 random character > > post bfb099c3b3f1 (BUG/MEDIUM: bad length in log_format and __send_log) > behavior: > every syslog message ends with \n + 2 random characters (usually \n, \0 or ") The behavior also depends on the syslog facility; I used "syslog" in my tests. With the current git tree I see the following behavior: ntp and local7: syslog ends with \n <-- correct behavior! ftp and user: syslog ends with \n + 2 random characters kern: syslog ends with \n + 4 random characters It seems 2a4a44f0f9f caused the initial problem and bfb099c3b3f1 amplified it. Regards, Lukas
