[imp] nearly every action results in being logged out

[Michael Ruddock]

Hi Aria

Thank you for replying, you have given me some great leads to explore.
I will definitely investigate everything you've mentioned. Thanks for your
help.

Best Regards


On 7 April 2014 20:44, Aria Bamdad <aria at bsc.gwu.edu> wrote:

>
> >If I change the Horde setting will this also fix the inode problem or do I
> >need to set something else?
>
> This list is not the appropriate place for questions regarding your
> ecommerce application.  Setting the values for Horde's session variables
> will ensure that the expired session files are deleted in /var file system
> if that is where you store your sessions.  Another thing to make sure you
> have properly setup is the values for session.gc_probability,
> session.gc_divisor and session.gc_maxlifetime in your PHP.INI file normally
> located under /etc/php5/apache2 if you use apache.
>
> Regarding your other application, perhaps you should separate the location
> of stored session files for this so that they do not interfere with your
> Horde sessions.  You can look at the PHP manual for session.save_path
>
> You should not setup a cron job to just delete ALL session files every so
> often.  You can however setup a cron job that deletes file older than a
> certain number of days based on how long you want a session to last.  There
> are examples of this online.
>
>
> --
> imp mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>