Hi,
Am 12.04.2016 um 19:39 schrieb Shawn Heisey:
I copied a front end to set up a new service on my haproxy install. I changed the name of the front end, but forgot to change the port number on the "bind" option. Haproxy didn't complain about this configuration when I tested for validity, so I didn't realize I'd made a mistake until the original service whose frontend I had copied began to fail. Is there a config option that would cause multiple front ends bound to the same address/port to be an invalid config? I am not running with multiple processes.
I think an option to disable SO_REUSEPORT would be handy (and only default to SO_REUSEPORT in daemon/systemd mode), so we can actually restore pre linux-3.9 behavior avoiding multiple binds to the same port, if we have that requirement.
However config check will never try to bind a port, it just checks for valid configuration syntax.
Trying to warn the user against unkown use-cases seems like a bad idea to me, its complex and prone to false-positives.
lukas
