On May 15, 2008, at 5:12 PM, Neal Becker wrote:
Problem I see is that an external script that *unconditionally*
relaunches dovecot could be a terribly problem. It's better for dovecot to do it itself in this particular failure, because it's the only one who
knows that it was just a date issue, and relaunching is safe.
If someone wants to code this relaunching, feel free to do it and if
the code looks good I'll include it.
I'll maybe try fixing this some other way for v1.2 (verify all
timestamp comparison code, make timeout handling work if clock moves,
log only a warning. I'm not sure if I'm going to use a monotonic
clock, since I'd like to know when time moves backwards or too much
forwards and add some hooks there to do things like update dotlock
file mtimes).