Hi Peter,
On Fri, Sep 14, 2018 at 05:43:14PM +0200, Peter Fröhlich wrote:
> For your consideration, the doc patch with context.
> Please give me feedback if I should incorporate some other aspects.
Thank you, however as you can see below, your mailer mangled the patch
by wrapping some lines and making it unusable. Could you please send it
as an attachment instead ? Oh by the way, if you're doing your patches
by hand, it's generally better to perform the diff from one directory
above the development tree, or by prepending "./" in front of the file
names so that the patch always applies fine using "patch -p1". Example
in your case :
$ diff -u ./doc/configuration.txt{.edited,} > file.diff
thanks!
Willy
> --- configuration.txt 2018-09-14 17:35:35.000000000 +0200
> +++ configuration.txt.edited 2018-09-14 17:35:29.000000000 +0200
> @@ -4894,69 +4894,79 @@
>
> load-server-state-from-file { global | local | none }
> Allow seamless reload of HAProxy
> May be used in sections: defaults | frontend | listen | backend
> yes | no | yes | yes
>
> This directive points HAProxy to a file where server state from previous
> running process has been saved. That way, when starting up, before
> handling
> traffic, the new process can apply old states to servers exactly has if
> no
> reload occurred. The purpose of the "load-server-state-from-file"
> directive is
> to tell haproxy which file to use. For now, only 2 arguments to either
> prevent
> loading state or load states from a file containing all backends and
> servers.
> The state file can be generated by running the command "show servers
> state"
> over the stats socket and redirect output.
(...)
