ID: 3793
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: Documentation problem
Operating System: Windows 98
PHP Version: 4 .1.2
New Comment:
I did some testing as Mike did ([31 31 Mar 3:49am] [EMAIL PROTECTED])
and I try to see what is the exact value to be set for gc_maxlifetime
to work in my sistem.
BTW I use win2000+iis5+php4.2.2.
I was very surprised to see that value 37000 worked for a period of
time but later the minimum was 38000 and so on.
So it's something related to sistem time not files(to be considered
garbage) In fact garbage control in windows work like this:
at gc_maxlifetime seconds from midnight all other session files are
deleted - definitly a bug.
Corneliu
Previous Comments:
------------------------------------------------------------------------
[2002-08-16 21:32:13] [EMAIL PROTECTED]
The fact that the filebased session handler needs a filesystem with
atime support has now been documented.
------------------------------------------------------------------------
[2002-08-16 21:03:38] [EMAIL PROTECTED]
I really don't see anybody with any interest in writing code to make
this work on FAT filesystems. Don't run web servers on crap
filesystems. If you do, write your own session handler. Same goes for
filesystems where file modification timestamps are ignored. Write your
own session handler and manage the garbage collection yourself. We'll
need to document this, of course, so marking this as a documentation
problem.
------------------------------------------------------------------------
[2002-07-10 05:10:43] [EMAIL PROTECTED]
I've exactly the same problem with Windows 2000, php 4.2.0 and apache
1.3
------------------------------------------------------------------------
[2002-03-31 03:49:43] [EMAIL PROTECTED]
After I tried about a week, by just setting the lifetime VERY high
(40000 first), maybe I can give a hint:
With this very high value it worked, so I tried where exactly was the
critical point. It was somewhat about 32000. Slightly below, all
session files were deleted as described, slightly over not. But then
the error reoccurred with the same value.
After some tries I found out the following: I set back the time on the
server one hour and it worked again. Here the times and the critical
points:
At 9:24 local time : 30290
At 10:28 : 34100
34100-30290=3810, which would be 63.5 minutes when interpretad as
seconds, which is the server's time difference...
Since 10:28 means 37680 s since 0:00, there seems to be an additional
hour - maybe due to GMT setting (+1) I thought, but it was the
automatic daylight saving (or is it called summer time???) setting.
When turned off, at 9:45 the point was at 35100=9.75 hours...
I hope that helps... ;-)
-- mike
------------------------------------------------------------------------
[2002-03-31 02:56:29] [EMAIL PROTECTED]
It seems it never worked under windows.
Reopen
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/3793
--
Edit this bug report at http://bugs.php.net/?id=3793&edit=1
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
