I found another issue with this cron job today. One of our web servers was experiencing very high load, I assumed we had high traffic and went to take a look at where the traffic was coming from.
It wasn't website traffic at all. We had so many PHP session files in the folder that the cron had failed to delete all the files within 30 minutes, in fact we had 6 cron jobs running at the same time. This almost brought the server to it's knees. Yet another reason to loose this cron job. -- PHP session garbage collection https://bugs.launchpad.net/bugs/316441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
