On Fri, Sep 18, 2009, Nick Mathewson wrote:
Right now most of the clue is in the reference book thing I've started
writing. The source for it is here, in Git:
git://git.torproject.org/~nickm/git/lebook.git
Right.
I'm glad to apply patches or pull contributions from other people's
.
From: libevent-users-boun...@monkey.org
[mailto:libevent-users-boun...@monkey.org] On Behalf Of Clint Webb
Sent: Thursday, September 17, 2009 7:46 PM
To: libevent-users@monkey.org
Subject: [Libevent-users] Must delete events before closing the socket
handle
Hello everyone,
After
.
From: libevent-users-boun...@monkey.org
[mailto:libevent-users-boun...@monkey.org] On Behalf Of Clint Webb
Sent: Thursday, September 17, 2009 7:46 PM
To: libevent-users@monkey.org
Subject: [Libevent-users] Must delete events before closing the socket
handle
Hello everyone
On Fri, Sep 18, 2009 at 10:57:25AM +0800, Adrian Chadd wrote:
Well, the order of which you can do this depends on what the underlying OS
will
do for you.
I'd suggest sticking to delete event, close socket usage. Anything else
isn't portable.
Nick, is this actually documented anywhere?
On Thu, Sep 17, 2009, Nick Mathewson wrote:
Nick, is this actually documented anywhere?
Not that I recall, and it really ought to be. Anybody want to write the
documentation patch?
I've been threatening to do this for ages. I may as well start now.
Is there a project wiki or something
...@monkey.org
[mailto:libevent-users-boun...@monkey.org] On Behalf Of Clint Webb
Sent: Thursday, September 17, 2009 7:46 PM
To: libevent-users@monkey.org
Subject: [Libevent-users] Must delete events before closing the socket
handle
Hello everyone,
After spending over a week
On Thu, Sep 17, 2009 at 07:51:58PM -0700, Gilad Benjamini wrote:
I just resolved a similar issue today, where I needed to close a file
descriptor AFTER deleting an event.
My symptoms, though, were different.
What underlying mechanism is your libevent using ?
In my case it is epoll. With
On Fri, Sep 18, 2009 at 11:09:52AM +0800, Adrian Chadd wrote:
On Thu, Sep 17, 2009, Nick Mathewson wrote:
Nick, is this actually documented anywhere?
Not that I recall, and it really ought to be. Anybody want to write the
documentation patch?
I've been threatening to do this for
