Differences Between Signal Handling between Solaris and DU

From: Patrick Farley <farley_at_Manassas1.TDS-GN.LMCO.COM>
Date: Fri, 06 Nov 1998 08:45:51 -0500 (EST)

We are running Digital Unix 4.0D and Solaris 2.6.

I have an application that establishes a set of pipes then exec's a second application/process.
The two processes communicates through the pipes. Should process two die for any reason a SIGPIPE will be generated when process one tries to send it data. I have to catch this signal, log it, and restart the second application/process. My SIGPIPE signal handler works as expected on the SUN. The problem is the target machine is a DEC ALPHA and things do not go as expected/desired. The signal handler catches the SIGPIPE signal but process one dies due to the receipt of a SIGSYS signal. I don't know why this signal is being generated on the DEC ALPHA and not on the SUN, nor do I know what to do about it. The bottom line/end goal is "if the pipe is broken don't die restart the second process". Any suggestions/comments/advice?

Thanks!
Received on Fri Nov 06 1998 - 13:46:50 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT