Re: [courier-users] possibly bug or misconfiguration? corrupted log lines in courier-imap

2008-01-09 Thread Sam Varshavchik
Thomas Jacob writes: On Fri, 2008-01-04 at 19:34 -0500, Sam Varshavchik wrote: An OS issue. Looks like Solaris doesn't line-buffer stderr, by default. Try sticking setvbuf(stderr, NULL, _IOLBF, BUFSIZ); as the first order of business in main() in both imaplogin.c and imapd.c. That should ta

Re: [courier-users] possibly bug or misconfiguration? corrupted log lines in courier-imap

2008-01-09 Thread Thomas Jacob
On Fri, 2008-01-04 at 19:34 -0500, Sam Varshavchik wrote: > An OS issue. Looks like Solaris doesn't line-buffer stderr, by default. > > Try sticking setvbuf(stderr, NULL, _IOLBF, BUFSIZ); as the first order of > business in main() in both imaplogin.c and imapd.c. > > That should take care of it

Re: [courier-users] possibly bug or misconfiguration? corrupted log lines in courier-imap

2008-01-04 Thread Sam Varshavchik
Thomas Jacob writes: Jan 4 00:22:19 XXX pop3d: [ID 702911 mail.info] LOGIN, user=XINFO: LOGIN, user=, ip=[:::XX.XX.XX.XX], port=[XXX2609, ip=[] Basically it looks like several client processes log messages aren't cleanly separated into single lines. We're running courier-authlib-0.60.

[courier-users] possibly bug or misconfiguration? corrupted log lines in courier-imap

2008-01-04 Thread Thomas Jacob
Hi everyone, We're seeing quite a number of corrupted log lines (~0.5% of log lines), where 2 different log messages seem to be overlapping or something like that. A typical example (XXX=privacy deletions): Jan 4 00:22:19 XXX pop3d: [ID 702911 mail.info] LOGIN, user=XINFO: LOGIN, user=, ip=[