Re: [Libevent-users] Must delete events before closing the socket handle

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 select or poll my scenario had no problems, in spite of the wrong order.

[Libevent-users] Empty read event

Hi, I am using libevent-1.4.11-stable and running into a problem within the epoll code. In epoll_dispatch, epoll_wait returns with a single event. The event has EPOLLIN set, but evread is NULL. Apparently, since the descriptor wasn't read, the event keeps happening over and over. Any ideas ?

[Libevent-users] Compatibility for dynamic linking

My program dynamically links to libevent. If I compile with 1.4.8, will it properly work on machines where 1.4.9 is installed ? And the other way around ? ___ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listin

[Libevent-users] Compatibility for dynamic linking

My program dynamically links to libevent. If I compile with 1.4.8, will it properly work on machines where 1.4.9 is installed ? And the other way around ? ___ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/

[Libevent-users] libevent and SIGPIPE

Hi, My program gets a SIGPIPE while in evbuffer_write The obvious solution is to ignore SIGPIPE. In a thread dating to Jan 08, I read that I should ignore the signal using standard sigaction calls, and not via libevent. What's the logic behind that ? In the mentioned thread, the application was m