[imp] nearly every action results in being logged out

[Michael Ruddock]

Hi Aria,

Thanks for replying, I appreciate your help.

Slightly off topic I apologise but I am really stuck and would be grateful
for any help.

My website fell over, my server provider said the server had ran out of
inodes and that I needed to delete the contents of /var/lib/php/session
This took about 3 days to delete going from 650k inodes down to 190k inodes.
Then they said I needed a chron job to keep on top of the contents of
/var/lib/php/session
So I added a chron job to the chrontab that deleted the contents once a
minute.
The result, my email broke and my ecommerce shopping cart stopped working.
I changed the chron job to run every 60 minutes, Email seems fine but my
shopping cart is still broken.
Are these 2 problems symptoms of the same problem? i.e. I am deleting stuff
from the /var/lib/php/session folder too quickly?

If I change the Horde setting will this also fix the inode problem or do I
need to set something else?

Cheers


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

>
> >I think I've fixed this.
> >I had a chron job that deleted all the session variables from the
> >/var/lib/php/session folder
> >I changed the chron job to run once every 60minutes and email seems back
> to
> >normal
> >Anyone got any experience could you tell me if this is too short an
> >interval?
>
>
> You should not be deleting files from your PHP sessions directory manually.
> Set the maximum length of your session by changing the Horde configuration
> option $conf[session][max_time] (under the 'General' tab of the Horde
> configuration settings via the GUI).  Then PHP should cleanup this
> directory
> automatically.  If you want to clean up manually, then you should only
> remove files from there that are older than the maximum age you specified.
>
>
> --
> imp mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>