On Tue, Jan 26, 2016 at 08:33:14PM +0100, Lukas Tribus wrote: > When a connect() to a unix socket returns EAGAIN we talk about > "no free ports" in the error/debug message, which only makes > sense when using TCP. > > Explain connect() failure and suggest troubleshooting server > backlog size.
Definitely makes sense, applied. Thanks Lukas! Willy
