16 Oct
2005
16 Oct
'05
1:36 p.m.
On Wed, 2005-09-28 at 13:47 -0400, Glenn Leavell wrote:
Where are you logging to? Syslog or some file? Could you try if changing it to other one makes it work again? Also when this happens, could you run "truss -p <dovecot's pid>" and see if it's still doing write() calls to log?
I've been logging to a file. The problem doesn't appear to be present when logging through syslog.
Did you have info_log_path set? Looks like if log_path is set but info_log_path isn't, it breaks. Although with me it crashes instead of stopping writing.