memcp gets expiration time wrong about libmemcached HOT 5 CLOSED

• Comment by: lp:~aaronm:
• Created at: 2013-12-16T17:36:42Z

I'm seeing this same issue on CentOS 5.6 and Ubuntu 12.04.

CentOS 5.6 with libmemcached version 1.0.4-3.el5

Ubuntu 12.04 with libmemcached version 0.42 and 0.44

As libmemcached evaluates the expire time differently depending upon if the seconds passed are < 30 days, it's worthwhile to note the same anomaly is seen with a much smaller value.

echo "Y" > testkey
memcp --verbose --debug --servers=localhost --expire=120 testkey
op: set
source file: testkey
length: 1
key: testkey
flags: 0
expires: 288

from libmemcached.

• Comment by: lp:~brianaker:
• Created at: 2014-02-01T23:49:27Z

The < 30 day expiration trick is how Memcached itself works. libmemcached is just the transport.

from libmemcached.

• Comment by: lp:~3-eail-2:
• Created at: 2014-02-02T00:09:39Z

Did you even read my original ticket? It has nothing to do with the 30 day behaviour.

from libmemcached.

• Comment by: lp:~brianaker:
• Created at: 2014-02-02T03:17:50Z

Hit the wrong field :)

The bug is how the number is being read (one fix coming up).

from libmemcached.

Fixed in 34ca5a8

from libmemcached.