MEDIUM: log-forward: use "dgram-bind" instead of "bind" for the listener

The use of "bind" wasn't that wise but was temporary. The problem is that
it will not allow to coexist with tcp. Let's explicitly call it "dgram-bind"
so that datagram listeners are expected here, leaving some room for stream
listeners later. This is the only change.
This commit is contained in:
Willy Tarreau 2020-09-16 15:07:22 +02:00
parent f9feec2813
commit 76aaa7f5b7
2 changed files with 7 additions and 6 deletions

View File

@ -2749,11 +2749,12 @@ haproxy will forward all received log messages to a log servers list.
log-forward <name>
Creates a new log forwarder proxy identified as <name>.
bind <addr> [param*]
Used to configure a log udp listener to receive messages to forward.
Only udp listeners are allowed, address must be prefixed using
'udp@', 'udp4@' or 'udp6@'. This supports for all "bind" parameters
found in 5.1 paragraph but most of them are irrelevant for udp/syslog case.
dgram-bind <addr> [param*]
Used to configure a UDP log listener to receive messages to forward. Only UDP
listeners are allowed, the address must be prefixed using "udp@", "udp4@" or
"udp6@". This supports for some of the "bind" parameters found in 5.1
paragraph among which "interface", "namespace" or "transparent", the other
ones being silently ignored as irrelevant for UDP/syslog case.
log global
log <address> [len <length>] [format <format>] [sample <ranges>:<smp_size>]

View File

@ -3610,7 +3610,7 @@ int cfg_parse_log_forward(const char *file, int linenum, char **args, int kwm)
px->id = strdup(args[1]);
}
else if (strcmp(args[0], "bind") == 0) {
else if (strcmp(args[0], "dgram-bind") == 0) {
int cur_arg;
static int kws_dumped;
struct bind_conf *bind_conf;