[imp] Log errors with memcached sessions

Kevin M. Myer kevin_myer at iu13.org
Wed Dec 7 19:36:01 PST 2005


Quoting liam hoekenga <liamr at umich.edu>:

> I've found if I use this patch, and my logging level is set to
> PEAR_LOG_DEBUG, that the browsers spins a lot, and I eventually get
> sent to the horde portal screen (where the browser continues to spin),
> rather than imp.
>
> If I've got my logging set to PEAR_LOG_EMERG, I'm fine.

Same here.  I have not put my finger on the exact reason that it does 
that, but I know with certain versions of glibc that are less forgiving 
about memory access, it would cause Apache to segfault.  I added the 
PEAR_LOG_DEBUG entries because I thought they would be helpful to track 
down problems, not create new ones :/

I did see in the PECL memcache CVS code that support for pooled servers 
has been added to the "official" extension.  There are also some leaks 
cleaned up.  I'm going to try and test this when I get a chance.  The 
algorithm for hashing is the same one I used, but its nice to have that 
supported in the API, instead of having to roll your own.  As I'm 
thinking about adding a memcached driver for the Horde Cache class, I 
might look at pulling the config for memcached into its own tab and 
then you could use the same settings for sessions and caching.

Kevin
-- 
Kevin M. Myer
Senior Systems Administrator
Lancaster-Lebanon Intermediate Unit 13  http://www.iu13.org




More information about the imp mailing list