25 May
2010
25 May
'10
5:35 a.m.
On Tue, May 25, 2010 at 1:06 PM, Alan DeKok <aland@deployingradius.com> wrote:
reedho@gmail.com wrote:
This behavior not seen when logging to files or syslog, only when set to stdout/stderr. So, my best guess after looking the source is that logging to stdout/err does not go to same processing flow as the others.
I have searching for this issue but still no luck, do I miss something?
It looks like there should be a call to setlinebuf() when logging to stdout and stderr.
I'll put a fix into git, but it looks like it's not in 2.1.9.
Thanks, --just feels unlucky sent this just a moment after 2.1.9 released. Best regards, --- Ridho