> From: [email protected]
> Date: Wed, 25 Mar 2015 12:42:21 +0100
> Subject: Re: Which signal causes HAProxy to reload its config
> To: [email protected]
> CC: [email protected]
>
> On 25 March 2015 at 12:25, jeff saremi <[email protected]> wrote:
>> I have to do manually what "-sf" is supposed to be doing since it's either
>> not working or not supported and removed.
>> I know what that does is send a signal to the pid stored by the haproxy
>> process. I'd like to do that myself.
>> Just need to know the signal name.
>> thanks
>> jeff
>
> Haproxy doesn't reload its config.
> -sf is there so that the new haproxy you're spawning tells the old one
> to stop accepting new connections and exit once the current one are
> closed.
> You do not send a signal to the running haproxy process (well, you do,
> but not only), you *replace* it.
>
> What you may be looking for, though, is haproxy-systemd-wrapper, which
> does all this automatically when it receives SIGUSR2 or SIGHUP.
>
> Regards,
> Marc-Antoine
Thank you so much Marc-Antoine. Finally someone took the time to answer this
properly.
