RE: [Libevent-users] Read failures on Unix socket

2010-11-05 Thread Gilad Benjamini
Gilad Benjamini > Sent: Thursday, November 04, 2010 10:01 PM > To: libevent-us...@freehaven.net > Subject: RE: [Libevent-users] Read failures on Unix socket > > > -Original Message- > > From: nick.a.mathew...@gmail.com [mailto:nick.a.mathew...@gmail.com] > On &

RE: [Libevent-users] Read failures on Unix socket

2010-11-04 Thread Gilad Benjamini
> -Original Message- > From: nick.a.mathew...@gmail.com [mailto:nick.a.mathew...@gmail.com] On > Behalf Of Nick Mathewson > Sent: Thursday, November 04, 2010 12:20 PM > To: Gilad Benjamini > Subject: Re: [Libevent-users] Read failures on Unix socket > > On Thu

RE: [Libevent-users] Read failures on Unix socket

2010-11-04 Thread Gilad Benjamini
> Hm. Looking at the epoll output in the "nonblocking" case, it doesn't > look like Libevent is doing anything weird here: epoll_wait() is > honest-to-goodness saying "Okay to read on fd 15"... > > 23:08:05 epoll_wait(4, {{EPOLLIN, {u32=15, u64=15}}}, 32, 0) = 1 > > ...but the recvfrom is saying

Re: [Libevent-users] Read failures on Unix socket

2010-11-03 Thread Nick Mathewson
On Tue, Nov 2, 2010 at 2:56 PM, Gilad Benjamini wrote: > I have a simple piece of code which used to work with libevent 1.4 and now > fails with 2.x Same drill as last time: I tried hacking up example code to match your description, and can't reproduce the behavior you're seeing, so there's proba

RE: [Libevent-users] Read failures on Unix socket

2010-11-02 Thread Gilad Benjamini
Indeed SOCK_DGRAM > -Original Message- > From: owner-libevent-us...@freehaven.net [mailto:owner-libevent- > us...@freehaven.net] On Behalf Of William Ahern > Sent: Tuesday, November 02, 2010 12:50 PM > To: libevent-us...@freehaven.net > Subject: Re: [Libevent-users] Rea

Re: [Libevent-users] Read failures on Unix socket

2010-11-02 Thread William Ahern
On Tue, Nov 02, 2010 at 03:13:02PM -0400, Simon Perreault wrote: > On 2010-11-02 14:56, Gilad Benjamini wrote: > > - Open a Unix socket > > - Bind to a socket in the file system > > - Add an event with EV_READ and EV_PERSIST > > - Wait for events > > - When an event arrives, call recvfrom on the so

Re: [Libevent-users] Read failures on Unix socket

2010-11-02 Thread Simon Perreault
On 2010-11-02 14:56, Gilad Benjamini wrote: > - Open a Unix socket > - Bind to a socket in the file system > - Add an event with EV_READ and EV_PERSIST > - Wait for events > - When an event arrives, call recvfrom on the socket waiting for a fixed > size of ~1800 bytes Aren't you supposed to listen

[Libevent-users] Read failures on Unix socket

2010-11-02 Thread Gilad Benjamini
I have a simple piece of code which used to work with libevent 1.4 and now fails with 2.x The basic operation - Open a Unix socket - Bind to a socket in the file system - Add an event with EV_READ and EV_PERSIST - Wait for events - When an event arrives, call recvfrom on the socket waiting for a f