On December 9, 2011 13:30 , Stormy <storm...@stormy.ca> wrote:
Apache2 2.2.17 on a possibly overbuilt (8 core CPU, 8 Gigs RAM, solid
state + raid drives) lightly loaded server using MySql, Perl and PHP.
Built using 'worker' rather than 'prefork' (Googling seemed to suggest
performance improvement under light loads) but now I'm reading various
reports that PHP could be troublesome (Debian User forum, "PHP5
stopped working".)
Am I paranoid? I found this while trying to find out about
.apache2.conf.swp and am now totally confused. Insight from the
experts here would save my sanity.
What are you confused about? Anyone can have problems with any software
system, PHP is not unique in this regard, nor is Apache. Things very
rarely just "stop working", though, there is always an underlying
reason, even if it is not readily apparent. This is why skilled system
administration and good service management practices are so important.
.apache2.conf.swp sounds like a temporary file created by vim or vi when
editing apache.conf. It's possible that the editor was killed or died
while apache2.conf was being edited, leaving the .swp file behind.
PHP has had long-standing thread safety issues. The "worker" MPM for
Apache HTTP Server is threaded. This can create problems and
instability. See
http://www.php.net/manual/en/faq.installation.php#faq.installation.apache2
If you want to use PHP, either use the "prefork" MPM or FastCGI.
--
Mark Montague
m...@catseye.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
