Oops. Thank you, Clint. First variant is exactly what i need. Don't
mention my previous email. :)
2009/6/26 Clint Webb :
> SIGPIPE happens normally because you attempt to write to a socket that has
> closed.
>
> There are a couple of things you can do...
>
> 1. You can disable SIGPIPE notificatio
Hi, Clint. Thanks for the answer. But I was interested how can i solve
it in the scope of libevent.
As u see, it's a pipe from libevent, so I thought, that I should check
it by libevent's tools or kind of... should I use your suggestions
anyway?
2009/6/26 Clint Webb :
> SIGPIPE happens normally be
SIGPIPE happens normally because you attempt to write to a socket that has
closed.
There are a couple of things you can do...
1. You can disable SIGPIPE notification. Something like:
struct sigaction sa;
sa.sa_handler = SIG_IGN;
sa.sa_flags = 0;
if (sigemptyset(&sa.sa_mask) == -1 || sigaction
Hi Rauan,
Set your daemon to ignore SIGPIPE.
Or register an empty signal handler for SIGPIPE.
Code from my own daemon that had this too:
if(signal(SIGPIPE, SIG_IGN) == SIG_ERR)
... print errno
Best regards,
Wouter
On 06/26/2009 09:01 AM, Rauan Maemirov wrote:
> Hi, all.
> I'm havin
Hi, all.
I'm having issues with libevent.
When I use siege or something like that, everything's ok. But when I
open link in browser, and start to push F5 like a crazy, daemon exits.
Valgrind shows:
...
Process terminating with default action of signal 13 (SIGPIPE)
==5635==at 0x5B2BF90: write
