Date: 11/25/99
- Next message: Zeev Suraski: "[PHP-DEV] Bug #2707"
- Previous message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #2700 Updated: include/require paths different"
- In reply to: David Hedbor: "[PHP-DEV] Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?"
- Next in thread: David Hedbor: "[PHP-DEV] Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
Just so you know, the dependencies are really messed up in PHP 4. If you're
switching between ZTS and non-ZTS mode make sure you at least do a make
clean before recompiling. You should probably even be doing a make distclean.
This could definitely result in random crashes.
Andi
At 09:15 AM 11/24/99 -0800, David Hedbor wrote:
>Sascha Schumann <sascha <email protected>> writes:
>
> > On Wed, Nov 24, 1999 at 02:30:11PM +0100, Thies C. Arntzen wrote:
> > > On Wed, 24 Nov 1999, Sascha Schumann wrote:
> > >
> > > > > 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)
> > > >
> > > > If the module does not work in ZTS mode, NO_GLOBAL_LOCK does
> > > > nothing.
> > >
> > > right, but i think that the plan should be to be able to run in ZTS mode
> > > without GLOBAL_LOCK? the roxen module (like aolserver and zeus) should
> > > run in ZTS and should allow more that one page at a time.
> >
> > I agree with that; the problem here is that a SAPI module
> > developer would have to track two moving targets. The first
> > one is PHP, the second one is the SAPI module. For debugging,
> > this is a ridiculous situation, because problems might be
> > caused by PHP or the SAPI module. The global lock disables
> > multi-threaded execution of scripts, therefore avoiding the
> > thread-safety issues of PHP.
>
>That is actually more or less the same thing I already implemented. In
>any case, I do of course want the module to work with ZTS mode, but
>after trying to get anything to work for hours (and just getting weird
>sigsegvs that didn't make much sense) I tried disabling it and it
>worked.
>
>If someone has tips/tricks on what should be done differently in ZTS
>module, I would really appreciate it. I want to run PHP in threaded
>mode, basically. I've tried looking in the other SAPI modules but it
>didn't help me much unfortunately.
>
>--
>[ Below is a random fortune, which is unrelated to the above message. ]
>You can go anywhere you want if you look serious and carry a clipboard.
>
>
>--
>PHP 4.0 Beta Mailing List <http://www.php.net/version4/>
>To unsubscribe, e-mail: php4beta-unsubscribe <email protected>
>For additional commands, e-mail: php4beta-help <email protected>
>To contact the list administrators, e-mail: php4beta-admin <email protected>
--- Andi Gutmans <andi <email protected>> http://www.zend.com/-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Zeev Suraski: "[PHP-DEV] Bug #2707"
- Previous message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #2700 Updated: include/require paths different"
- In reply to: David Hedbor: "[PHP-DEV] Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?"
- Next in thread: David Hedbor: "[PHP-DEV] Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

