PHP 4.0 Bug #8670 Updated: Incorect interpretation session.gc_maxlifetime parameter

ID: 8670 Updated by: sniper Reported By: vgo@nrd.lt Old-Status: Open Status: Feedback Bug Type: *Configuration Issues Assigned To: Comments: 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 Previous Comments: --------------------------------------------------------------------------- [2001-01-15 01:24:50] vgo@nrd.lt Incorect interpretation session.gc_maxlifetime parameter, the other session parameters: session.save_handler = files session.save_path = C:PHPsessiondata 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-14 17:30:33] sniper@php.net What are the other session related php.ini values you have? --Jani --------------------------------------------------------------------------- [2001-01-12 04:17:56] vgo@nrd.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. --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=8670