Re: Sessions not destroyed
| From: | Hendrik Schmieder | Date: | Fri, 08 Oct 2004 14:13:34 +0000 |
| Subject: | Re: Sessions not destroyed | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-198960@lists.php.net to get a copy of this message | ||
Marek Kilimajer schrieb:
Hendrik Schmieder wrote:If the current sesions timed out, since there was no action in the session lifetime, then the session file must be deleted. On the other side, if there's an action in the session lifetime, the timer for this session should be reset to zero. Anyway , if the apache service is stopped (I am not speaking about a crash) all session files must be deleted. HendrikMarek Kilimajer schrieb:Depends on your point of view. It is a sideeffect of loading current session (and thus accessing it) before the session gc is called. So the question is, should the session module give up on current session just because it should have been garbaged, even if the session file still exists? That's the point.Hendrik Schmieder wrote:OK , changed in php.ini, but no change in behaviour.Hello, we have a severe problem with seesions. We use Apache 1.3.31 with PHP 4.3.9 as Apache module in Windows 2000 In our php.ini we have session.gc_probability = 100Should be session.gc_divisorsession.gc_dividend = 100And you need to start at least one other session so that the first one gets cleared.If you are right, then this is a severe design bug.