Re: $_SESSION v. Cookies

On Wed, May 7, 2008 at 2:35 PM, Robert Cummings <robert@interjinn.com> wrote: > > On Wed, 2008-05-07 at 14:29 -0600, Nathan Nobbe wrote: > > On Wed, May 7, 2008 at 2:22 PM, Robert Cummings <robert@interjinn.com> > > wrote: > > > > On Wed, 2008-05-07 at 16:03 -0400, tedd wrote: > > > At 12:34 PM -0400 5/7/08, Robert Cummings wrote: > > > > > > > >The exception being when it performs cleanup. Cleanup > > should be > > > >relegated to a cron job. > > > > > > Rob: > > > > > > What clean-up? > > > > > > All the inactive session files... inactive and garbage > > collection time > > is denoted by the following php.ini settings: > > > > session.gc_probability = 1 ; percentual probability > > that the > > ; 'garbage collection' > > process is > > ; started > > ; on every session > > initialization > > session.gc_maxlifetime = 1440 ; after this number of > > seconds, > > ; stored data will be seen as > > ; 'garbage' and cleaned up by > > the > > ; gc process > > > > so where is the setting, using the stock session handler, to relegate > > the gc process to a cron job ? > > session.gc_probability = 0 > but wont it still try to run sometimes since that setting determines whether or not the gc will run *every* time ? i would imagine if it was for *any* time, setting session.gc_probability = 0 would effectively disable the stock gc. Then do it yourself in a script called by cron. it would be nice if you could latch into the one they provide out of the box and just invoke it via cron.. -nathan