Issue 351 in memcached: memcp uses wrong expiration time

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 351 by m...@thomasbachem.com: memcp uses wrong expiration time http://code.google.com/p/memcached/issues/detail?id=351 The {{{memcp}}} ({{{memccp}}}on Debian systems) command line utility gets the supplied expire time wrong:

Re: Issue 351 in memcached: memcp uses wrong expiration time

Updates: Status: Invalid Comment #1 on issue 351 by dorma...@rydia.net: memcp uses wrong expiration time http://code.google.com/p/memcached/issues/detail?id=351 Please file this against libmemcached. this is memcached, the server side. remember to include the version of the library y

Re: CAS Delete support in any Python memcached client?

On Thu, 12 Dec 2013, mumb...@gmail.com wrote: > Hi all, > > Just tried (and failed) to find any Python client with support for the > new-ish CAS operations on the binary protocol (i.e. CAS delete etc.). Does > anyone know of one - or have any plans for one? Or is there a fork of the C > libmemca

Re: memcached server irreponsive

Hi, If you're still seeing issues at all; can you try 1.4.16, and use the "memcached-debug" binary instead of the normal one? That should give more useful information on the crash. There should hardly be any lock contention at 5 threads unless you are running an older version... The latest code s

Re: please tell me memcached" command guide ! where doc url?

It's all here bro: http://code.google.com/p/memcached/wiki/NewStart Regards, __ Filippe Costa Spolti Linux User n°515639 - http://counter.li.org/ filippespo...@gmail.com "Be yourself" On 12/14/2013 0