On 7/11/11 11:22 AM, James Bardin wrote:
On Mon, Jul 11, 2011 at 2:18 PM, Alexander Hollerith
<[email protected]> wrote:
Thank you very much for pointing me into that direction. I think that definitely answers
my question. Since haproxy itself might keep more than one process alive after dealing
with an "-sf" (at least for as long as it takes to finish the work) I assume
that keeping alive more than one process, in principle, can't be a problem :)
Another FYI, the included init script does this on automatically
reload, and prefaces it with a config check to prevent killing the
process altogether.
-jim
AFAIK, if there are config problems haproxy won't start a new process but it
also won't kill the old one when using -sf.
