If I fork an app and push thousands of connections through polipo with the app configured to use it as a http proxy, and the socks5 host that polipo is supposed to be talking to is down, polipo stacks up those thousands of connections in the open file table and jams up the system. And they don't go away after the app has long since exited. Nor does a kill -usr2 clear them. I didn't test what happens when the host comes back up as that is a non-solution.
Shouldn't these connections have a settable timeout period? using ver of 20110802... polipo socksParentProxy=127.0.0.1:9050 socksProxyType=socks5 clientTimeout=190 serverIdleTimeout=180 serverTimeout=180 logLevel=0xFF ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
