Do you have something specific in mind that might be causing this? It looks like under normal circumstances the alarms are set and the caught, but sometimes it looks like two of the signals are received in quick succession, the first clears the signal mask, and the second causes the default handler to be called, which means the process dies. Quite frustrating.
-aaron On Fri, Aug 02, 2002 at 02:54:17PM -0700, Rasmus Lerdorf wrote: > I'm surprised it worked at all. Start with CVS versions of both and go > from there. > > On Fri, 2 Aug 2002, Cody Sherr wrote: > > > > > > > We are having difficulty getting PHP 4.2.2 to play nicely with Apache > > 2.0.36 configured with a prefork mpm on Solaris 2.8. The child processes > > keep dying with uncaught SIGALRM's. This problem disappears when php is > > removed from the apache configuration. I've attached a truss output. Has > > anyone else experienced this problem, and if so, what was your solution? -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
