Summary | horde_sessionhandler table grows bigger and bigger |
Queue | Horde Base |
Queue Version | 3.3.6 |
Type | Bug |
State | Not A Bug |
Priority | 2. Medium |
Owners | |
Requester | michael (at) bigmichi1 (dot) de |
Created | 12/20/2009 (5673 days ago) |
Due | |
Updated | 12/21/2009 (5672 days ago) |
Assigned | 12/21/2009 (5672 days ago) |
Resolved | 12/21/2009 (5672 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Not A Bug
Bug: 8792check for session gc values
http://cvs.horde.org/diff.php/horde/test.php?rt=horde&r1=1.193&r2=1.194&ty=u
direction with these php.ini settings, but still it would be nice to
have these checked in test.php from horde
setting for "session.gc_probability = 0", can there be some sort of
check in the test.php, that looks for that configuration values?
State ⇒ Feedback
http://www.php.net/manual/en/session.configuration.php#ini.session.gc-divisor
http://www.php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime
http://www.php.net/manual/en/session.configuration.php#ini.session.gc-probability
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ horde_sessionhandler table grows bigger and bigger
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
based sessions). i think there should be some sort of garbage
collector running on the table. the code in mysql.php has a gc
function but i can't find a call to this function in the entire code.
my horde_sessionhandler table has now 10267 entries. and when running
the sql 'select * from horde_sessionhandler where
`session_lastmodified` < 1261306002' with 1261306002 is time() - 300 i
got 10265 entries listed with the oldest timestamp is 1257691733. and
this is really old.