Please keep threads on the list.
Quoting Matthew Dunham <[EMAIL PROTECTED]>:
I've confirmed that these problems don't exist in Horde 3.2.1/IMP 4.2,
so the trigger is clearly something that's been introduced in the past
months' development efforts. Just for fun I disabled caching,
thinking this new feature might be the culprit -- but no dice.
Which caching feature did you disable? There are a number of
different ones; several are called out in the accompanying comments
as ones that increase session size, which might lead to memory
growth in httpd processes.
ah, the new horde object caching system (if that's what you call it).
$conf['cache']['driver'] = 'file';
i'm using this setting in production, but see the same behavior with:
$conf['cache']['driver'] = 'none';
That will definitely not hurt you and may hurt. You should look
through the IMP settings for things that might increase session size -
I don't have them in front of me right now, sorry.
-chuck
--
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [EMAIL PROTECTED]
