php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #8670 Incorect interpretation session.gc_maxlifetime parameter
Submitted: 2001-01-12 04:17 UTC Modified: 2002-01-09 02:02 UTC
From: vgo at nrd dot lt Assigned:
Status: Closed Package: Session related
PHP Version: 4.0.4 OS: Windows 2000
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: vgo at nrd dot lt
New email:
PHP Version: OS:

 

 [2001-01-12 04:17 UTC] vgo at nrd dot lt 
This parameter is not correctly interpreted. In my experiments if I specify 36000 (Aprox 10 hours) the gc process removes sesion imediately. If 360000 session will be removed aroximately after 10 days.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-01-14 17:30 UTC] sniper@php.net 
What are the other session related php.ini values you have?

--Jani
 [2001-01-15 01:24 UTC] vgo at nrd dot lt 
Incorect interpretation session.gc_maxlifetime parameter, the other session parameters:
session.save_handler      = files
session.save_path         = C:\PHP\sessiondata
session.use_cookies       = 0
session.name              = PHPSESSID
session.auto_start        = 1
session.cookie_lifetime   = 10000000
session.cookie_path       = /
session.cookie_domain     = 
session.serialize_handler = php
session.gc_probability    = 100
session.gc_maxlifetime    = 360000
session.referer_check     = 
session.entropy_length    = 0
session.entropy_file      = 
session.cache_limiter     = nocache
session.cache_expire      = 1
session.use_trans_sid     = 1
 [2001-01-15 04:23 UTC] sniper@php.net 
You do understand that with this setting:
session.gc_probability    = 100
the garbage collection is started every time
you run a script? (ie. 100 = 100%) 

How did you found out that the session is removed?
Any example scripts? It sounds really odd that 
36000 didn't work but 360000 did.

--Jani
 [2001-01-15 05:55 UTC] vgo at nrd dot lt 
The session.gc_probability set to 100% during experiments with lifetime. I expected some king of timeout of my site during subsiquent acceses. So I started to experiment with that and I wrote what I got. The script examples is any with session_register, with session.auto_start enabled, but I tried with session_start and got the same result. I gues that this might be something with time interpreting on the Win32 platform, cause the problem seems to be solved when life time set to more than 24 hours.
 [2001-12-19 22:07 UTC] yohgaki@php.net 
It could be file locking problem.
Please test with 4.1.0 and snapshot, and report the result.

http://snaps.php.net/
 [2002-01-09 02:02 UTC] lobbin@php.net 
No feedback. Closing.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Wed May 07 14:01:30 2025 UTC