Re: syslogd tls read write events

2015-09-18 Thread Bob Beck
ok beck@ On Fri, Sep 18, 2015 at 5:17 PM, Alexander Bluhm wrote: > On Fri, Sep 18, 2015 at 05:04:55PM -0600, Bob Beck wrote: >> ... and just to be clear, you only need to event_del when you are >> switching to wanting a write when you did want a read before, and vice >> versa... correct? > > Yes.

Re: syslogd tls read write events

2015-09-18 Thread Alexander Bluhm
On Fri, Sep 18, 2015 at 05:04:55PM -0600, Bob Beck wrote: > ... and just to be clear, you only need to event_del when you are > switching to wanting a write when you did want a read before, and vice > versa... correct? Yes. When I am doing reads and get a TLS_WANT_POLLOUT, I have to do a event_se

Re: syslogd tls read write events

2015-09-18 Thread Bob Beck
... and just to be clear, you only need to event_del when you are switching to wanting a write when you did want a read before, and vice versa... correct? if that's the case it reads ok... On Fri, Sep 18, 2015 at 4:55 PM, Alexander Bluhm wrote: > Hi, > > I discovered what caused the strange eve

syslogd tls read write events

2015-09-18 Thread Alexander Bluhm
Hi, I discovered what caused the strange event loss in syslogd during the hackaton. I had mixed EV_READ and EV_WRITE events on the ev_read and ev_write event structures. The correct way is to use each event for its read and write purpose and instead switch the handler. Then libevent is no longe