RepoMirrors/haproxy
1
0
Fork 0
mirror of http://git.haproxy.org/git/haproxy.git/ synced 2025-04-11 03:31:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

DOC: logs: the format directive was missing from the second log part

Browse Source 
The "log" statement appears both in the global section and in listeners.
The "format" directive was only documented in the first one. Maybe we
should think about moving this definition to the log section by now.
This commit is contained in:
Willy Tarreau 2018-11-12 07:56:13 +01:00
parent 251fe34ca2
commit adb345d485
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/configuration.txt
View File

@ -5066,7 +5066,7 @@ load-server-state-from-file { global | local | none }
log global
log <address> [len <length>] <facility> [<level> [<minlevel>]]
log <address> [len <length>] [format <format>] <facility> [<level> [<minlevel>]]
no log
Enable per-instance logging of events and traffic.
May be used in sections : defaults | frontend | listen | backend
@ -5116,6 +5116,15 @@ no log
generally fine for all standard usages. Some specific cases of
long captures or JSON-formatted logs may require larger values.
<format> is the log format used when generating syslog messages. It may be
one of the following :
rfc3164 The RFC3164 syslog message format. This is the default.
(https://tools.ietf.org/html/rfc3164)
rfc5424 The RFC5424 syslog message format.
(https://tools.ietf.org/html/rfc5424)
<facility> must be one of the 24 standard syslog facilities :
kern user mail daemon auth syslog lpr news