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 multi-threaded. Mine is single. Would that change the recommendation ? Does libevent itself fork additional threads ?
Beyond ignoring the signal, any ideas about why libevent is actually getting the signal ? Can I count on libevent to recover cleanly from this event ? Thanks Gilad _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
