Re: Re: ps_mm_initialize() always called
| From: | Rasmus Lerdorf | Date: | Fri, 05 Oct 2001 15:57:17 +0000 |
| Subject: | Re: Re: ps_mm_initialize() always called | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-67354@lists.php.net to get a copy of this message | ||
I have seen a number of people getting "Unable to start session mm module
in Unknown on line 0" errors even when they aren't using mm as their
session handler.
See:
http://bugs.php.net/bug.php?id=13379
http://bugs.php.net/bug.php?id=13320
http://bugs.php.net/bug.php?id=13268
http://bugs.php.net/bug.php?id=13095
-Rasmus
On Fri, 5 Oct 2001, Sascha Schumann wrote:
> On Fri, 5 Oct 2001, Rasmus Lerdorf wrote:
>
> > Sascha, do you think it would be possible to move that call out of the
> > MINIT function in MINIT? It doesn't make a lot of sense to me to
> > initialize mm if it is not being used. Especially since this could fail
> > and prevent people from using file-based sessions.
> >
> > Perhaps the right fix is to check if the session handler is mm in MINIT
> > and also stick that initialization in the onupdate ini handler.
>
> Nope, that would make it impossible to switch save handlers,
> because the shared memory segment has to be initialized from
> the parent process (anonymous shared memory).
>
> MINIT is executed exactly once per "apachectl (re)start" and
> only if you have explicitly build PHP with MM support. Could
> you elaborate on where you see a problem?
>
> - Sascha Experience IRCG
> http://schumann.cx/
> http://schumann.cx/ircg
>
>
>