PHP Source Dump
| From: | Richard Lynch | Date: | Sat, 09 Dec 2000 21:59:49 +0000 |
| Subject: | PHP Source Dump | ||
| Groups: | php.qa | ||
| Request: | Send a blank email to php-qa+get-1785@lists.php.net to get a copy of this message | ||
Since the current theory is that it happens when somebody is editing the
config file and/or httpd is starting up or shutting down, maybe somebody who
can shell script (not me) could devise some sort of stress test where Apache
is started/stopped a lot, and the output of a PHP script is compared to the
two possibilities it should be: either the normal page or, er, whatever
error you get when httpd is dead.
Admittedly, this is a bit more complicated than the ab of a running server,
but I think it might be a good place to focus.
If we can (well, okay, more "you" than "we" since the implementation would
take "me" days or weeks) reliably show that this happens during
startup/shutdown of Apache, we'll know the following:
A) That the concern is quite small, and that what the reports are saying
probably coincides with startup/shutdown of httpd
B) We (you) can focus on making that not happen -- After all, if somebody
*is* concerned about IP and/or security, telling them they only need to
worry during startup/shutdown of httpd is like telling them they can only
rely on the rhythm method for birth control. Not really good enough for
some people's tastes/beliefs. It will probably entail a change to Apache
rather than PHP, but presumably that's not impossible for a reasonably
security patch.
Disclaimer: It's entirely possible I've misunderstood something in this
thread that makes everything I've typed sheer nonsense. Sorry.