tree e3a880fc5a56fdd818b203e2060724bf5854810f
parent ce036bc2daec3bb407f801f1bab366ee383b76b0
author Willy Tarreau <w@1wt.eu> 1517234764 +0100
committer Willy Tarreau <w@1wt.eu> 1517235534 +0100
encoding latin1

MINOR: fd: don't report maxfd in alert messages

The listeners and connectors may complain that process-wide or
system-wide FD limits have been reached and will in this case report
maxfd as the limit. This is wrong in fact since there's no reason for
the whole FD space to be contiguous when the total # of FD is reached.
A better approach would consist in reporting the accurate number of
opened FDs, but this is pointless as what matters here is to give a
hint about what might be wrong. So let's simply report the configured
maxsock, which will generally explain why the process' limits were
reached, which is the most common reason. This removes another
dependency on maxfd.