On Wed, Aug 1, 2012 at 1:34 PM, Eric Wong <[email protected]> wrote: > > Hey all, this is probably a sensible change to make for unicorn 4.4.0 > > > > There's a small chance of introducing an incompatibility if an app > > somehow internally depends on having a listen socket ready while it's > > loading. A test case to avoid one breakage with Raindrops::Middleware > > is included. > > > > (original bug reporter Bcc-ed) > > Any comments? I'm leaning towards applying this to master
I would like to see this on master. It would definitely benefit us here at New Relic. In addition to the case of a listener being bound that can't yet serve requests, we also have some trouble caused by forked processes inheriting the listen sockets during the application startup. Not binding them until afterwards would allow us to remove our special case code around that. -Nic _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
