From: Cyril Bonté Date: Thu, 23 Mar 2017 21:44:13 +0000 (+0100) Subject: MEDIUM: global: add a 'hard-stop-after' option to cap the soft-stop time X-Git-Tag: v1.8-dev1~53 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=203ec5a2b566bfd731538ad4ea21a849b79412ad;p=thirdparty%2Fhaproxy.git MEDIUM: global: add a 'hard-stop-after' option to cap the soft-stop time When SIGUSR1 is received, haproxy enters in soft-stop and quits when no connection remains. It can happen that the instance remains alive for a long time, depending on timeouts and traffic. This option ensures that soft-stop won't run for too long. Example: global hard-stop-after 30s # Once in soft-stop, the instance will remain # alive for at most 30 seconds. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 73a4f4b82e..fb3e691d5f 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -536,6 +536,7 @@ The following keywords are supported in the "global" section : - external-check - gid - group + - hard-stop-after - log - log-tag - log-send-hostname @@ -703,6 +704,22 @@ gid will only be able to drop these groups if started with superuser privileges. See also "group" and "uid". +hard-stop-after