memcp uses wrong expiration time

GoogleCodeExporter commented 8 years ago

The {{{memcp}}} ({{{memccp}}}on Debian systems) command line utility gets the 
supplied expire time wrong:

{{{
memcp --verbose --servers=localhost --set --expire=1418563176 "foo:bar"
op: set
source file: foo:bar
length: 4
key: foo:bar
flags: 0
expires: 86307647862
Calling memcached_free()
}}}

Providing a value of {{{54900000}} leads to {{{1418723328}}}, which brings me 
very near to my desired expiration time of {{{1418563176}}}.

I tested this on Mac OS X 10.8.5 and Linux Debian 7.2.

Original issue reported on code.google.com by m...@thomasbachem.com on 14 Dec 2013 at 2:10

GoogleCodeExporter commented 8 years ago

Please file this against libmemcached. this is memcached, the server side.

remember to include the version of the library you're using/etc.

Original comment by dorma...@rydia.net on 14 Dec 2013 at 8:18

Changed state: Invalid

GoogleCodeExporter commented 8 years ago

Oh, of course, thanks. For reference: 
https://bugs.launchpad.net/libmemcached/+bug/1261128

Original comment by m...@thomasbachem.com on 15 Dec 2013 at 11:48

funly / memcached

memcp uses wrong expiration time #351