Re: Re: session.gc_maxlifetime

Hi Tom, in sometimes 2001 I did have incidences with those things, and as I remember over the past years there where some trouble with operating systems and stuff. This part is very deep inside the os. I would expect that this is still to consider. I also would check, if this occurs on very busy/low memory server. If I would programm the garbage collection clean up part, and if the server is about to run out of memory, I would kill sessions being longer time idle even when they are not yet as old as it is set in the gc_maxlifetime. This would be far better then shutting down the whole server just because there a 100 of idle sessions waiting to get used again. as u mention a maxlivetime of 6h I would bet, that this is the problem. I would not trust such a long lifetime at all. If sessions have to be active such a long time, I would see only cooky based solutions let me know, what u did investigate on this. ralph_deffke@yahoo.de "Tom Worster" <fsb@thefsb.org> wrote in message news:C6DEAE55.12CAE%fsb@thefsb.org... > thank you, Ralph! > > i'm going to be bold and assume that tom at punkave dot com is right despite > that the report was discarded. > > i got a complaint from a client about some users reporting being logged out > with rather short periods of inactivity. but session.gc_maxlifetime is set > to 6 hours so i don't think that's the source of the problem. > > > On 9/22/09 4:17 PM, "Ralph Deffke" <ralph_deffke@yahoo.de> wrote: > > > Hi Tom, > > > > i did find this in the bug reports, its pretty new and should be an answer. > > > > http://news.php.net/php.doc.bugs/2653 > > > > ralph_deffke@yahoo.de > > > > > > "Tom Worster" <fsb@thefsb.org> wrote in message > > news:C6DE9EEE.12C8D%fsb@thefsb.org... > >> i'm not 100% sure what the manual means when it says... > >> > >> session.gc_maxlifetime integer > >> session.gc_maxlifetime specifies the number of seconds after which data > > will > >> be seen as 'garbage' and cleaned up. Garbage collection occurs during > >> session start. > >> > >> what event exactly does the "after which" here refer to? > >> > >> i'd like to think that it means that a session is eligible for gc no > > sooner > >> than session.gc_maxlifetime seconds after the most recent access (read or > >> write) to that session. but it seems dangerously presumptuous to assume > > that > >> this is the case. > >> > >> what do you take it to mean? > >> > >> > > > > > >