Currently, if haproxy tries to start up and a webserver is down (and it's defined as a hostname in the config file) haproxy refuses to start. Looking at the previous change logs and announcements it seems this is by design. Why is this done and is there a way to circumvent this?
I would consider this a rather large design flaw, I must be missing something. Cheers
