session.save_path = "N;/path"
| From: | Wez Furlong | Date: | Wed, 09 Oct 2002 08:19:12 +0000 |
| Subject: | session.save_path = "N;/path" | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-89271@lists.php.net to get a copy of this message | ||
I thought that I'd try this out with HEAD, but I found that PHP would
go into an infinite loop. I didn't have time to debug it, so I reverted
to using a regular path instead. Could a session guru take a look and
double check this?
session.save_path="2;/var/tmp" --> infinite loop
session.save_path="/var/tmp" --> works just fine
If there isn't an obvious problem, I'll try to get a backtrace later tonight.
--Wez.
> Colin Viebrock wrote:
> > cmv Mon Oct 7 13:58:27 2002 EDT
> >
> > Modified files:
> > /php4 php.ini-dist
> > Log:
> > Document session.save_path option in php.ini
> > Index: php4/php.ini-dist
> > diff -u php4/php.ini-dist:1.161 php4/php.ini-dist:1.162
> > --- php4/php.ini-dist:1.161 Thu Oct 3 02:52:23 2002
> > +++ php4/php.ini-dist Mon Oct 7 13:58:27 2002
> > @@ -766,6 +766,15 @@
> > +; As of PHP 4.2.3, you can define the path as:
> > +; session.save_path = "N;/path"
> > +; where N is an integer. Instead of storing all the session files in
> > +; /path, what this will do is create subdirectories N-levels deep, and
> > +; store the session data in those directories. This is useful if you
> > +; or your OS have problems with lots of files in one directory, and is
> > +; a more efficient layout for servers that handle lots of sessions.
> > +; (Note: see the section on garbage collection below if you choose to
> > +; use subdirectories for session storage)