> I was just trying to make a point
You did make a point, but totally different from the one intended.
Also your proposed fix is incomplete...
# sed -n -e
's/^[[:space:]]*session.save_handler[[:space:]]*=[[:space:]]*\([[:alnum:]]\+\).*$/\1/p'
/etc/php5/fpm/php.ini
# php5 -c /etc/php5/fpm/php.ini -d "error_reporting='~E_ALL'" -r 'echo
ini_get("session.save_handler")."\n";'
files
The cron job is really meant for the default setup, since it also has
other problems:
* The cron job doesn't handle custom session.save_path
* The cron job doesn't catch session files in subdirectories
> If you seriously think running lsof on a server every 30 minutes
regardless of the necessity is perfectly safe, then I guess we can agree
to disagree :)
If you can come up with a better way how to skip and not delete session
files that are still used by long running scripts (e.g.
https://bugs.debian.org/626640), then I would gladly accept the new
solution.
I am also going to improve the wording of README.Debian to accent the
need to modify the cron job if you modify the session handling.
** Bug watch added: Debian Bug tracker #626640
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626640
--
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
--
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
