mahara-contributors team mailing list archive

[Nigel Cunningham <nigelc@xxxxxxxxxxxxxxx>]

This doesn't seem right to me. Mahara's internal cron system includes a
task for invoking auth_remove_old_session_files in auth/lib.php.

Perhaps the Mahara cron task wasn't being run on the system in question?
(Next scheduled run times are recorded in the cron table - if a task has
never run, nextrun will be NULL).

-- 
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:
  In Progress

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