Seems this SQL from gc() function in class.t3lib_userauth.php. Here deleted old sessions - you can change class variables:
var $gc_time = 24; // GarbageCollection. Purge all session data older than $gc_time hours. var $gc_probability = 1; // Possibility (in percent) for GarbageCollection to be run. Set gc_time less than 24 and gc_probability set more than 1 (it's mean that ~one from every 100nd showed page will ask to delete old sessions) "Søren Madsen" <[email protected]> ???????/???????? ? ???????? ?????????: news:[email protected]... Every morning at 9AM it seems like TYPO3 instructs our database server to run a clean up job. We se lots of jobs like this one: > | 455212 | typo3 | ourserver.dk:36821 | typo3s | Query | 59 | Locked | > DELETE FROM fe_sessions > WHERE > ses_id = 'b0ba76d6971a84a4455eeaf4916dd20b' > AND ses_nam The problem is that these jobs locks the server, and makes all of our sites unresponsive or they throw a database user denied error, and this takes 5-10 minutes. We can't seem to find the origin of these jobs - can anyone help ? We obviously don't mind that these clean up jobs run, but we'd really like to know where they come from, and we'd really like to change the time they run. Kind regards, Søren Madsen _______________________________________________ TYPO3-english mailing list [email protected] http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
