Re^2: Is this a bug of perl threads?

"The signal is sent to the whole process"? Is this mean that when I interrupt a client process, the signal SIG_INT will be send to the whole server process through the socket?

Comment on Re^2: Is this a bug of perl threads?

Replies are listed 'Best First'.
Re^3: Is this a bug of perl threads? by ikegami (Patriarch) on Mar 12, 2010 at 03:10 UTC
No, I was just thoroughly confused. What's the exit status of the server (`server.pl ; echo $?`)? ( According to almut below, this would have indicated the server died from SIGPIPE. Have a problem? Check for errors! ) Is there a parent-child relationship between the server and the clients? The fact that the same socket is being used by multiple threads is odd...	[reply] [d/l]
Re^4: Is this a bug of perl threads? by Ray.Zachary (Acolyte) on Mar 12, 2010 at 03:48 UTC
The exit code is 141.	[reply]
Re^5: Is this a bug of perl threads? by ikegami (Patriarch) on Mar 12, 2010 at 04:33 UTC
141-128 = 13, and `kill -l` will show that to be SIGPIPE	[reply] [d/l]