Re: Re: Re: sysvsem extention question
| From: | Jason Greene | Date: | Fri, 24 Aug 2001 14:14:49 +0000 |
| Subject: | Re: Re: Re: sysvsem extention question | ||
| References: | 1 | Groups: | php.dev php.general |
| Request: | Send a blank email to php-dev+get-64248@lists.php.net to get a copy of this message | ||
----- Original Message -----
From: "Sascha Schumann" <sascha@schumann.cx>
To: "Jason T.Greene" <jason@inetgurus.net>
Cc: "Tom May" <tom.may@infospace.com>; "Chris Chabot"
<chabotc@reviewboard.com>; <php-dev@lists.php.net>;
<php-general@lists.php.net>
Sent: Friday, August 24, 2001 1:49 AM
Subject: Re: [PHP-DEV] Re: Re: sysvsem extention question
> > parent process right before fork. There is no parent
> > initializer for a php module author
>
> MINIT() is called from the parent process in forking servers.
> The mm storage handler uses this hook to instantiate a shared
> memory segment and propagate the handle to all child
> processes.
Sascha is right...
Allow me to reword..
There is no way to allow a php file author the ability to execute php source during
module startup of a forking web server. The module would have to allocate and
initialize all semaphores before the php source is parsed. This defeats the purpose
of a semaphore extension in a forking webserver environment, becuase the php source
author would be limited to just the semaphors allocated by the php module.
-Jason
> - Sascha Experience IRCG
> http://schumann.cx/
> http://schumann.cx/ircg
>