Signal 13 on a socket connection?

I have a task that terminated on a signal 13, “broken pipe”. It did not
have a pipe open, but it was using a socket connection to another
computer on the LAN. Any idea what this would mean?

Thanks,

Kevin

Hi Kevin:

If one end of a TCP socket is closed or gets killed and the other end
attempts to send to it, a broken pipe error should occur. You should
check and see if the associated connection on the other computer is
still alive.

Robert.



Kevin Miller wrote:

I have a task that terminated on a signal 13, “broken pipe”. It did not
have a pipe open, but it was using a socket connection to another
computer on the LAN. Any idea what this would mean?

Thanks,

Kevin

If you set signal(SIGPIPE, SIG_IGN); the send() / write()
will fail with -1 and errno EPIPE.

-seanb

Robert Craig <rcraig_at_qnx@nowhere.com> wrote:

Hi Kevin:

If one end of a TCP socket is closed or gets killed and the other end
attempts to send to it, a broken pipe error should occur. You should
check and see if the associated connection on the other computer is
still alive.

Robert.



Kevin Miller wrote:
I have a task that terminated on a signal 13, “broken pipe”. It did not
have a pipe open, but it was using a socket connection to another
computer on the LAN. Any idea what this would mean?

Thanks,

Kevin