* Thus wrote Jason Barnett: > >On garbage collection, it happens sometimes within seconds and sometimes > >within minutes. It tends to occur in batches with lulls of 20 to 30 > >minutes. So, for example, I can login, navigate through 11 different pages > >to generate the problem, navigate 2 pages to generate the problem, and then > >not see the problem again for another 5 minutes. Does that fall in line > >with what you're thinking? > > > > Actually, no. Garbage collection would destroy the sessions, so if > they're only "temporarily" disappearing then load balancing seems even > more likely. > > I'm going to assume not, but are you using a non-default session > handler? If for instance you were storing sessions in another database,
or using the default handler, and the /tmp dir is full. Garabage Collection cleans up things so it works for a while until it fills up again, then breaks again (possibly saving a session or two with the minimal disk) till GC decides to kick in again. df -ih /tmp/ Check Avail and ifree. Curt -- First, let me assure you that this is not one of those shady pyramid schemes you've been hearing about. No, sir. Our model is the trapezoid! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
