# Pastebin 2lnoW2wj
Looks like we are going to need to fix our FD limit bug:
strict-limits: we've all been used to see haproxy warn on startup that
    it didn't have enough FDs to allocate the required number of connections
    but startup nevertheless. A number of people got caught in production
    with this, especially more recently with systemd where warnings do not
    appear on the console by default anymore. The new "strict-limits"
    directive makes haproxy refuse to start when conditions are not met. It
    is not enabled by default but the default will change in 2.3 to be turned
    on in order to avoid surprises. You have one more year to check your
    configs :-)