Is there a graceful shutdown of imapd process?

[nodens2099]

Le 19/11/2009 19:13, Dan Smith a écrit :
> My goal is to be able to reload the imapd.conf file for imap processes 
> without impacting currently connected subscribers.
> I know that there are some patches available to allow this to be done 
> with a SIGHUP, but until they are widely accepted and one is brought 
> into the code thread, we will probably shy away from it.
>  
> I was wondering if another approach would be possible.
> Is there any way that anyone can think of of that would stop an imapd 
> process from taking on new connections without impacting the existing ones?
>  
> If there were, I could block new connections for one process at a time 
> and when all connections were drained off, restart it.
>  
> Any other ideas about how to accomplish this?
>  

Actually, the SIGHUP handling patch as been in debian packages (2.2.x) 
for a while now. This is a pretty large audience, and AFAIK no problem 
has been reported on this feature.

Anyway, if you are on linux (or *BSD), a good solution would be to 
prevent new connections via netfilter/iptables (or pf for BSD), while 
allowing "established" data flow, using the stateful firewalling.

The problem is, most modern clients try to stay connected...

Best regards,

-- 
Clément Hermann (nodens)