Tom and list, The problem with the solaris builds is a compilation one. Some optimisation flags were used to the Sun compiler that broke the builds. New builds will be released soon. Sorry for any inconvenience. nick > Nick, > > Sorry for the late reply. Yes, if I cleanup the shared memory and > temporary files, do a restart, and hit a simple phpinfo() script the > problem occurs immediately. Here is the Apache error log output: > > [Fri Mar 8 20:12:15 2002] [notice] Apache/1.3.22 (Unix) PHP/4.1.2 > configured -- resuming normal operations > [Fri Mar 8 20:12:15 2002] [notice] Accept mutex: fcntl (Default: > fcntl) [Fri Mar 8 20:12:41 2002] [notice] child pid 25545 exit signal > Bus Error (10) > The system is a Sun Fire 280R with 4gb ram and dual UltraSPARC-III CPUs > running Solaris 5.8. Please let me know if I can do anything to help > debug this problem. > > Best Regards, > > Thomas Duffey > >>> Nick, >>> >>> After upping the maximum available shared memory on a SunOS 5.8 >>> server I started getting tons of these messages in Apache's error >>> log (only with phpa enabled): >>> >>> [Wed Feb 27 15:55:57 2002] [notice] child pid 23248 exit signal Bus >>> Error (10) >>> >>> Pages are served, but every process dies with this error. I'm >>> running >>> PHP 4.1.2 and phpa 1.2p3. Any ideas? >> >> Tom, >> >> If you do a totally clean restart - i.e. remove the phpa_ cache files, >> stop apache, checking that the shared memory has been deleted (it >> should do so itself), and then restarting - do you get errors >> immediately? >> >> Can you also send me the error log from the time of the restart to the >> segfaults. >> >> nick ------------------------------------------------------------------------ www.php-accelerator.co.uk Home of the free PHP Accelerator To post, send email to phpa@xxxxxxxxxxxxx To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject unsubscribe