On Jun 9, 2009, at 1:54 PM, Harlan Stenn wrote:
Timo wrote:
On Jun 9, 2009, at 1:03 PM, Eugene wrote:
But really, all this leads is that admin has to detect the dovecot
termination and simply go and restart it manually -- after some bad
thoughts.
Or the admin actually permanently fixes the time.
This is usually a startup issue and the fact that so many OSes get
this
wrong and that dovecot complains about it so strongly points out this
"rough edge".
And I already mentioned in this thread that I could try to get that
fixed:
Hmm. I suppose I could change Dovecot master so that if no imap/pop3
processes have been created yet, it would silently ignore the clock
move.
