On Wed, May 18, 2016 at 02:29:14AM +0200, Robert Eisele wrote:
> directly accepting 0 byte reads after the first byte was read. Is this a
> problem with libev or am I missing something?
That's likely a problem with your code forgetting to close the fifo?
> epoll_wait(3, {{EPOLLHUP, {u32=5, u64=4
Hi,
I wanted to create a simple non-blocking fifo using libev. It works
great, but when I strace the process, I see a lot of epoll_waits
directly accepting 0 byte reads after the first byte was read. Is this a
problem with libev or am I missing something?
In more detail, the code can be found her
