Hi
I have a problem with my php, once in a while an apache process will hang.
In apache's /server-status it looks like:
*11-1*111941/3/588*W* 0.20213490179.30.2227.03 xxx.xxx.xxx.xxx
localhostGET xxx.php?xxx=xxxAs you can see from this line the process has
been working for 21349sec and the status
On 25.03.2010, at 18:07, Zeev Suraski wrote:
At 18:51 25/03/2010, Sebastian Bergmann wrote:
Zeev Suraski wrote:
What does it contain?
It looks to me as if the patch would also reduce the memory footprint:
That makes perfect sense... Thanks for sharing the results!
So where do we
Am 11.04.2010 16:21, schrieb Lukas Kahwe Smith:
So where do we stand here?
I was wondering the same.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runtime
On Sun, Apr 11, 2010 at 3:43 PM, Frederik Banke frede...@tigermedia.dkwrote:
Hi
I have a problem with my php, once in a while an apache process will hang.
In apache's /server-status it looks like:
*11-1*111941/3/588*W* 0.20213490179.30.2227.03 xxx.xxx.xxx.xxx
localhostGET xxx.php?xxx=xxxAs
Hi all.
I've been reading about the security implications of turning
allow_url_fopen 'on' for certain PHP applications that need
to read files from a remote URL.
To recap, please read this old article about Remote
file inclusion vulnerabilities: http://lwn.net/Articles/203904/
I'm just
On Sun, Apr 11, 2010 at 6:23 PM, Keith Roberts ke...@karsites.net wrote:
Hi all.
I've been reading about the security implications of turning
allow_url_fopen 'on' for certain PHP applications that need to read files
from a remote URL.
To recap, please read this old article about Remote
On Sun, Apr 11, 2010 at 6:23 PM, Keith Roberts ke...@karsites.net wrote:
Hi all.
I've been reading about the security implications of turning
allow_url_fopen 'on' for certain PHP applications that need to read files
from a remote URL.
To recap, please read this old article about Remote
A few people, well ok, Lukas mainly, seem to be confused about our
current process, or lack of it. I think it is pretty simple, and it is
what we used for years. We commit all new code to trunk. Bug fixes
should obviously be committed to any active branches they apply to as
well. When we have
Hello Moriyoshi,
Monday, April 5, 2010, 5:57:38 PM, you wrote:
While it is based on shared-nothing approach, some kinds of resources
are shared across threads besides classes and functions that would
have already been defined before the thread creation.
Maybe it would not be so hard
