[Bug 1356113] Re: PHP5 session clean cron job causes OOM

[Ondřej Surý]

> One problem with the solution you linked to is that it is extracting
the gx_maxlifetime in seconds, then putting that in find's -cmin which
expects minutes.

Good catch. The code was there, but it got deleted accidentally.

> What do you think about running this for each SAPI?

I am still not sure whether we are not breaking something with this
change, but it's very good idea.

I have incorporated the idea, but kept the one run per directory and
improved it that it just takes the highest gc_maxlifetime value. There's
also an optimization to run pidof only once, since iterating through
/proc/ on servers with many processes would also take it's toll
(although I doubt the common setups include more than one SAPI on the
server...)

Updated script is located in the git: http://anonscm.debian.org/cgit
/pkg-php/php.git/tree/debian/sessionclean

Could you please proofread it and test it on your servers?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1356113

Title:
  PHP5 session clean cron job causes OOM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1356113/+subscriptions