Re: check_client_connection using getsockopt(2)

Simon Eskildsen wrote: > On Wed, Feb 22, 2017 at 8:42 PM, Eric Wong wrote: > > Simon Eskildsen wrote: > >> I meant to ask, in Raindrops why do you use the netlink API to get the > >> socket backlog instead of

Re: check_client_connection using getsockopt(2)

On Wed, Feb 22, 2017 at 8:42 PM, Eric Wong wrote: > Simon Eskildsen wrote: > > Thanks for the writeup! > > Another sidenote: It seems nginx <-> unicorn is a bit odd > for deployment in a containerized environment(*). > >> I meant to ask, in Raindrops

Re: check_client_connection using getsockopt(2)

On Wed, Feb 22, 2017 at 1:33 PM, Eric Wong wrote: > Simon Eskildsen wrote: > > great to know it's still working after all these years :> > >> This confirms Eric's comment that the existing >> `check_client_connection` works perfectly on loopback, but