Process killed by SIGALRM randomly
807567Feb 16 2001 — edited Apr 14 2002Hi,
We have been observing a strange thing happening to our server processes (multithreaded) on Solaris 5.7. After running the servers for a while, they will be killed by "Alarm Clock". We are never explicitly using alarm in our code. So, the only thing that we can think of is the implementation of sleep because we do use sleep indirectly.
According to the POSIX standard, sleep can be implemented using alarm. The default action to SIGALRM is terminating the process. It seems to be the case now. So if sleep is implemented using alarm, is it possible that the signal handler that sleep registers somehow got lost and the default action is used? Could it be related to multithreaded applications with signals?
I appreciate any relevant information.
Thanks in advance,
Miranda