[RESOLVED] custom session handler ignores ini_set()

[sandthipe]

I've got a working custom session handler for MySQL, but I can't get the script to obey my ini_set clauses. The main problem I'm facing is in regards to the session expiration; if I ini_set the session.gc_maxlifetime to 60 (for testing purposes only), the handler reverts to the server default (1440 on my server). Any thoughts as to why the handler won't recognize the ini_set commands? Some facts about my setup:

1. i've got a separate file for all my ini_set clauses which is included on all pages

2. php5, apache 2.2.2

Here's my write function in the session handler

function mysql_session_write($sid, $value) {

  $lifetime = get_cfg_var("session.gc_maxlifetime");
  $expiration = time() + $lifetime;

  $query = "INSERT INTO sessions 
            VALUES('$sid', '$expiration', '$value')";
  $result = mysql_query($query);

  if (!$result) {
     $query = "UPDATE sessions SET 
               expiration = '$expiration',
               value = '$value' WHERE
               sid = '$sid' AND expiration >". time();
    $result = mysql_query($query);
 }
   }

Thanks in advance for any advice! -chris

[NogDog]

One possibility is that another PHP script which uses the same session data directory is running with the default gc_maxlifetime. If so, it will delete any session data in that directory that it determines is out of date. Therefore, you may need to have your script that does the ini_set calls also specify a separate session save path (either via ini_set() or the session_save_path() function).

[sandthipe]

Well, I'm using a db for session storage, and the funny thing is that the script does fine with the command to ini_set(session.cookie_lifetime, whatever); just won't take with the session.gc_maxlifetime.

Changing the session.save_path wouldn't affect a handler oriented to db storage, would it?

[sandthipe]

Well, I don't really consider this question resolved, but I decided to hard-code my desired expiry value into the handler rather than bother about the ini_set confusion any longer. I'm still curious as to why just that one value wouldn't take...

[NogDog]

I think the problem is using get_cfg_var() to get the value instead of ini_get(). It's not clear from the [man]get_cfg_var[/man] page, but the user comments seem to indicate that get_cfg_var() gets the original value from the php.ini file, not the value currently in effect for your script.