[PHP-DEV] Problem with streams on Windows (current PHP_5_1)

I am getting the following with current PHP_5_1 on Windows. No small reproducing script, yet. Debug Error! Program: c:\home\php\php-5.1\debug_ts\php.exe Module: c:\home\php\php-5.1\debug_ts\php5ts_debug.dll File: c:\home\php\php-5.1\main\streams\xp_socket.c Line: 641 Run-Time Check Failure #3:

[PHP-DEV] CVS Account Request: ibuleave

Development -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] reducing open calls in php

Sascha Schumann wrote: On Thu, 2 Feb 2006, Rasmus Lerdorf wrote: Sascha Schumann wrote: Or simply use eAccelerator which does not cause those open calls. Which doesn't support PHP 5.1 very well. Which is pretty fine for us PHP 4.4 users. The site where I reinstalled eAccele

Re: [PHP-DEV] reducing open calls in php

On Thu, 2 Feb 2006, Rasmus Lerdorf wrote: > Sascha Schumann wrote: > > Or simply use eAccelerator which does not cause those open > > calls. > > Which doesn't support PHP 5.1 very well. Which is pretty fine for us PHP 4.4 users. The site where I reinstalled eAccelerator does not

Re: [PHP-DEV] reducing open calls in php

Sascha Schumann wrote: Or simply use eAccelerator which does not cause those open calls. Which doesn't support PHP 5.1 very well. Rasmus, is that behaviour by design? I deinstalled APC because of this 'characteristic' last week. It was killing a high-traffic site. Lo

Re: [PHP-DEV] reducing open calls in php

I tested this and you are correct. This should make a big difference. I learn something new every day :) Thanks a million. -James Rasmus Lerdorf <[EMAIL PROTECTED]> wrote: > > I think the main hint you need is to never use require_once/include_once > with an opcode cache. Those are the

Re: [PHP-DEV] reducing open calls in php

Sascha Schumann wrote: Or simply use eAccelerator which does not cause those open calls. Rasmus, is that behaviour by design? I deinstalled APC because of this 'characteristic' last week. It was killing a high-traffic site. - Sascha On Thu, 2 Feb 2006, Rasmus Lerdo

Re: [PHP-DEV] reducing open calls in php

Or simply use eAccelerator which does not cause those open calls. Rasmus, is that behaviour by design? I deinstalled APC because of this 'characteristic' last week. It was killing a high-traffic site. - Sascha On Thu, 2 Feb 2006, Rasmus Lerdorf wrote: > I think the m

Re: [PHP-DEV] reducing open calls in php

I think the main hint you need is to never use require_once/include_once with an opcode cache. Those are the only ones that will cause an open() call. You should only be seeing a single stat() call per file under APC (needed to get the inode+device hash key for the shared memory lookup). -Ra

[PHP-DEV] reducing open calls in php

Hello: We have a very high-volume site that runs across a cluster of several machines which needs to have access to our back end storage platform, which needless to say is very busy. I have been given the task of reducing load to the filer. Due to the fact that our application is rather large a

[PHP-DEV] Re: PHP and Non-Apache

Haha, after looking over the enviorment variables one last time I noticed it was setting the content length to zero, my fault. After fixing this, it seems to be working! Yay, yet another webserver with php support :) www.sf.net/projects/ante Matthew wrote: > Sara Golemon wrote: > >>> Hello al

[PHP-DEV] Re: DATE_ISO8601 and the "c" date() character

On Tue, 31 Jan 2006, Hannes Magnusson wrote: > I just noticed that the DATE_ISO8601 constant and the "c" date() > character don't give the same results. > The difference is that the "c" format prints colon in the timezone > offset, but the constant does not - both are however ISO8601 > compliant.