I've read through the forums and searched on the internet, but was unable to find a similar situation that I am having.
The server I am using is Linux-Mandrake 7.1 with PHP 4.0.2 and accesses a Postgres DB.
I am writing an application using sessions where users log in and are able to get access to certain areas of the application based on a group they belong to. Due to having a captured audience (intranet), I use exclusivly cookies based now, and register only the SESSION variable as an object, and put all other variables in that. The user information is stored in $SESSION["user"][...]. The problem I am having is that it seems that when the garbage collection happens, it will blow away the current session that I am using. I variables in the SESSION variable regularly, and have the following configuration parameters:
Session Support enabled
session.auto_start Off
session.cache_expire 180
session.cache_limiter nocache
session.cookie_domain no value
session.cookie_lifetime 14400
session.cookie_path /
session.entropy_file no value
session.entropy_length 0
session.gc_maxlifetime 14400
session.gc_probability 1
session.name PHPSESSID
session.referer_check no value
session.save_handler files
session.save_path /tmp
session.serialize_handler php
session.use_cookies On
The one thought I had is that the SESSION["user"] object I place only when the user logs in and remove it only when the user logs out, so I was wondering if the garbage collection is the whole session, or each individual piece of info in the session file?
I'm at a loss and just short of doing manual garbage collection with a crontab, but would rather have the system take care of it.
Any help would be greatly appreciated,
Chad
