Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?
| From: | David Hedbor | Date: | Wed, 24 Nov 1999 18:00:41 +0000 |
| Subject: | Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory? | ||
| References: | 1 | Groups: | php.dev php.version4 |
| Request: | Send a blank email to php-dev+get-13066@lists.php.net to get a copy of this message | ||
"Thies C. Arntzen" <thies@digicol.de> writes:
> On 23 Nov 1999, David Hedbor wrote:
>
> > Well, that is not entirely a good idea. The Roxen module currently
> > doesn't use ZTS (actually doesn't work with it). It's still a problem
> > since Roxen itself is threaded. What I did is to have a mutex lock
> > that prevents running more than one PHP script at any one time. Maybe
> > it could simply be a configure option, that would be automatically
> > enabled by ZTS and Roxen (to take two examples)? Ie when ZTS is on, it
> > would be enabled w/o extra effort from the person compiling the
> > source.
>
> david,
>
> add NO_GLOBAL_LOCK to you CFLAGS - right now there's a global lock in
> main.c. (sascha put it in for some reason i forgot - maybe 'cause it
> wasn't as stable on with aolserver as we thought)
Well, this wouldn't help me since I can't get it to work in ZTS mode
even when I just run one script at once. This is probably mainly due
to me not knowing how to "ZTS-proof" it. :-)
> our goal for B4 should be to be fully thread-safe on unix & win32.
That is great news.
--
[ Below is a random fortune, which is unrelated to the above message. ]
The truth you speak has no past and no future. It is, and that's all it
needs to be.