The other day a friend of mine wrote to me that I had a problem with Debian -my server a. Its not exactly kept more than sessiite 30 No matter how many minutes to set up session.gc_maxlifetime. Basically the problem is that Debian have decided to re-write the conduct of sessions instead garbage collector-and start one cron every 9th and 39 minutes that cleans up old sessions. He is in/etc/cron.d/php5
overall, the sempličk script which in turn launches/usr/lib/php5/maxlifetime and variable how long is the life of the cookie that is 1440 seconds or 24 minutes from here on there is 😉 2 options or to stop the Crown and thus terminate the automatic cleaning which may later to realign the php. ini or directly in the script to change the life longevity of sessions with the variable max. I personally prefer the second option. Pretty neat is overall but there is a drawback – If you overwrite the file changes will be lost which is a troublesome fact.
ps. Now that I think about it probably if is defined somewhere else where to store the php info via seiinata should go beyond the scope of the script and thus to be used again in a normal session without interrupting rude.
ini_set('session.gc_maxlifetime', 14400); ini_set('session.gc_probability', 1); ini_set('session.gc_divisor', 100); session_save_path(APP_PARENT_DIR . '/sessions');