Re: Squid and SIGPIPE

Adrian Chadd wrote:
> On Thu, Jul 05, 2007, Amos Jeffries wrote:
>> I have been overlooking these for a while on the assumption that it was
>> gdb catching something when it should have left it. I have just started
>> wondering if this was in fact bad unexpected behaviour for the squid
>> signals. Should I be looking into it?
>
> Nope!
>
> put this in ~/.gdbinit:
>
> handle all nostop noprint
> handle SIGSEGV stop
> handle SIGPIPE stop
>

Thanks for that Adrian. I have tested it in my config now.
"handle SIGPIPE stop" did the opposite of what is wanted, "nostop print"
lets me know when they occur, but leaves squid running. I assume it was
a typos or version defaults difference?

Amos
Received on Sun Jul 08 2007 - 00:38:24 MDT