From: Willy Tarreau Date: Sat, 26 Jan 2019 13:20:55 +0000 (+0100) Subject: DOC: nbthread is no longer experimental. X-Git-Tag: v2.0-dev1~150 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1f672a8162eda18c404c6784dd749b6e061e2e4d;p=thirdparty%2Fhaproxy.git DOC: nbthread is no longer experimental. It was mentioned when releasing 1.8 but early bugs have long been addressed and this comment discourages some users from using threads. This should be backported to 1.9 and 1.8 now. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index e44b6579d6..55e56be5f7 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -958,14 +958,14 @@ nbproc mode. By default, only one process is created, which is the recommended mode of operation. For systems limited to small sets of file descriptors per process, it may be needed to fork multiple daemons. USING MULTIPLE PROCESSES - IS HARDER TO DEBUG AND IS REALLY DISCOURAGED. See also "daemon". + IS HARDER TO DEBUG AND IS REALLY DISCOURAGED. See also "daemon" and + "nbthread". nbthread This setting is only available when support for threads was built in. It creates threads for each created processes. It means if HAProxy is started in foreground, it only creates threads for the first - process. FOR NOW, THREADS SUPPORT IN HAPROXY IS HIGHLY EXPERIMENTAL AND IT - MUST BE ENABLED WITH CAUTION AND AT YOUR OWN RISK. See also "nbproc". + process. See also "nbproc". pidfile Writes PIDs of all daemons into file . This option is equivalent to