Hi Nick,
The fix worked, thank you!
Amarin
On Tue, Feb 21, 2012 at 7:42 PM, Nick Mathewson wrote:
> On Tue, Feb 21, 2012 at 8:17 PM, Amarin Phaosawasdi
> wrote:
> > We've written a very simple client and server in Libevent.
> [...]
> > Is this expected behavior?
>
> Thanks for helping to deb
> Also, a unit test that causes a great number of sockets to open and
> get closed would be pretty cool if somebody wants to write one.
>
Here we go:
Cheers
Ross Lagerwall
---
The following changes since commit 74d32dd493a9eba7ff8c28bc1cdf1d3c672edf5c:
If accept4 is absent, fall back to acce
On Tue, Feb 21, 2012 at 8:17 PM, Amarin Phaosawasdi
wrote:
> We've written a very simple client and server in Libevent.
[...]
> Is this expected behavior?
Thanks for helping to debug the master branch of Libevent! No,
leaking infinite sockets is never the correct behavior. (If you
didn't actua
We've written a very simple client and server in Libevent.
When we start up the server and have the client make thousands of requests
to the server, the client eventually ends with a "too many open files"
error. (The system that ran this had the ulimit set to 4096.)
This only happens at the clien
