Hi, this patch series attempts to allow haproxy to be restarted - perhaps reconfigured would be a better term - without refusing or dropping connections.
The model that I am using is that of a master process, which really does nothing but hold bound file descriptors, and workers - these should be very similar to what haproxy processes have looked like up to now. This feature can be enabled using the -M command line option of the master_worker configuration file option. It may be used in conjunction with daemon. In order to effect a restart a SIGUSR2 should be sent to the master process. The master process is guaranteed to be the first pid listed in the pid file. It will also be the parent process, and can thus be found using ps. It should also be noted in the logs. SIGUSR2 is ignored if master/worker mode is not enabled. SIGUSR2 is ignored by workers.
