Gentle shutdown feature

Rob Riepel riepel at networking.stanford.edu
Tue Jul 1 20:08:57 UTC 2014


On Jul 1, 2014, at 2:27 AM, Phil Mayers <p.mayers at imperial.ac.uk> wrote:

> On 27/06/14 16:35, John Wobus wrote:
> 
>> There are other similar sites that use the same "stop and
>> start frequently" strategy.  I would naturally be concerned
>> if the daemons had trouble ever reaching normal state.
> 
> Yes, we do this, and I agree.

Same here.

We generate a complete configuration every 10 minutes and restart the server if there are changes (with 1800+ shared networks and 222000+ host entries being updated by 800+ people it’s easier to keep things in sync by creating a new config than doing diffs and using OMAPI).

> It's really peculiar for a standard shutdown signal - INT or TERM - to result in the daemon not coming immediately back into service on the next startup.
> 
> Would recommend making it a different signal e.g. USR1 or an OMAPI command.

I suppose it boils down to what is a “standard” restart.  We can cope with using “kill -9” to facilitate a quick restart, but it seems wrong to do so.  If the consensus is that INT or TERM result in a checks and lengthy restart, it would be good to have a signal or OMAPI command that results in a quick restart.

--
Rob Riepel





More information about the dhcp-users mailing list