On Wed, 2006-04-12 at 21:42 +1000, Rob Middleton wrote:
What about the alternate kill signal to the master just stopping listening for new connections? (release the *:143 and *:110 handles).
If logging by syslog you can happily have two dovecot masters sending log lines ... won't work in other cases I suppose (suppose that is what I'm missing?)
With both a new master and an old master you can then also choose to go and do a proper kill on your old master 24 hours later or something like that to ensure nothing runs on the old binaries for longer than 24 hours (as a proper kill on the master now kills all the relevant children).
I guess that would work. The master itself doesn't listen for new connections, but it should just stop creating new login/auth processes. It could also kill itself automatically after all the log pipes get closed. But is it still worth it to do this? :)