"Interacting" with memcached has been a problem, since pretty much the only thing we can easily do with it is restart it to empty it of all cached values. This is less than ideal, especially in a multi-tenant setup where several Koha instances share the same server, and also the same memcached server. This is especially true when sessions are saved in memcached, which means that "flushing" (restarting) the cache for one site terminates all active sessions for all sites. 

koha-memcached tries to fix this by providing a convenient script to list all keys in memcached, get their values and delete them. This is done as a script similar to koha-mysql etc. 

Now, while researching this I read that doing things like listing all keys in memcached might not always be possible. It does seem to work in the testing I have done so far though. Maybe a single instance of memcached on localhost is less problematic in this respect then if you have a cluster of servers etc? More opinions on this is needed. 

The script relies on Memcached::libmemcached and memcdump. 

This is mostly a proof of concept, with some rough edges that need to be worked on a bit more, *if* this approach is something we think is worth pursuing. Feedback is most welcome!