I had a similar issue to Phil. A web server was generating PHP sessions faster than they were being deleted by the cron job. This caused the disk on which /var/lib/php5 was located to run out of inodes, and thence to a loss of service.
It is caused by this upstream workaround, which is poor:
I had a similar issue to Phil. A web server was generating PHP sessions faster than they were being deleted by the cron job. This caused the disk on which /var/lib/php5 was located to run out of inodes, and thence to a loss of service.
It is caused by this upstream workaround, which is poor:
http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 461755# 20
The latest version of the cron job that does PHP session garbage collection is here:
http:// anonscm. debian. org/gitweb/ ?p=pkg- php/php. git;a=blob; f=debian/ php5-common. php5.cron. d;hb=HEAD
It would probably be a good idea to backport to this LTS release, because it fixes Phil's issue, among other security concerns.