mahara-contributors team mailing list archive

[Aaron Wells <1324316@xxxxxxxxxxxxxxxxxx>]

Hah, I learn something new about Mahara every day! ;)

Yep, that cron task does indeed delete the old session files. Marking
this bug Invalid.

** Changed in: mahara
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1324316

Title:
  Old PHP sessions files never get deleted

Status in Mahara ePortfolio:
  Invalid

Bug description:
  As reported on the forum:
  https://mahara.org/interaction/forum/topic.php?id=6331

  Normally PHP session files get deleted by a cron job in the
  filesystem, that is installed as part of the PHP module (in Debian &
  Ubuntu). But Mahara does not store its session files in the default
  location. Instead, it overrides session.save_path to save session
  files in its own custom location under $CFG->dataroot.

  As a result, Mahara session files do not get regularly deleted, unless
  the server owner has changed their default location or set up a
  special cron job to clean them up (or if you're using the memcached
  patch for session management).

  We need to add a Mahara internal crontask that checks for old session
  files and deletes them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1324316/+subscriptions