threading issue : SIGPIPE => SIG_IGN (writing to closed socket)

From: Oliver Kowalke <oliver.kowalke@xxxxxx>
Date: Sat, 30 Dec 2006 11:34:31 +0100

Hello,
hopefully you can give me an answer how linux (kernel 2.6.x) reacts (I found
different opinoins in the inet):

In a multithreaded library a thread sets the sigaction SIG_IGN for signal
SIGPIPE if it tries to write to a socket and resets to the old sigaction
with SIG_DFL afterwards.

Will EPIPE allways be returned to the same thread if the socket was closed
before write (and RST was received)?

If yes is this guaranteed?

thanks and kind regards,
Oliver
.

Prev by Date: Re: One computer only on home net having DNS lookup trouble
Next by Date: Re: Problem in Networking at Kernel Level
Previous by thread: One computer only on home net having DNS lookup trouble
Next by thread: caching special kind of Web request
Index(es):
- Date
- Thread

Relevant Pages

Re: threading issue : SIGPIPE => SIG_IGN (writing to closed socket)
... In a multithreaded library a thread sets the sigaction SIG_IGN for signal ... Will EPIPE allways be returned to the same thread if the socket was closed ... the only way you can guarantee that ...
(comp.sys.hp.hpux)
SIGPIPE => SIG_IGN : EPIPE returned always to the thread raising SIGPIPE?
... In a multithreaded library a thread sets the sigaction SIG_IGN for signal ... SIGPIPE if it tries to write to a socket and resets to the old sigaction ... Will EPIPE allways be returned to the same thread if the socket was closed ...
(comp.unix.programmer)
threading issue : SIGPIPE => SIG_IGN (writing to closed socket)
... different opinoins in the inet): ... In a multithreaded library a thread sets the sigaction SIG_IGN for signal ... Will EPIPE allways be returned to the same thread if the socket was closed ...
(comp.os.linux.development.system)
threading issue : SIGPIPE => SIG_IGN (writing to closed socket)
... found different opinoins in the inet): ... In a multithreaded library a thread sets the sigaction SIG_IGN for signal ... Will EPIPE allways be returned to the same thread if the socket was closed ...
(comp.sys.hp.hpux)
Re: SIGPIPE => SIG_IGN : EPIPE returned always to the thread raising SIGPIPE?
... In a multithreaded library a thread sets the sigaction SIG_IGN for signal ... SIGPIPE if it tries to write to a socket and resets to the old sigaction ... Will EPIPE allways be returned to the same thread if the socket was closed ...
(comp.unix.programmer)