Updates:
Status: Fixed
Comment #1 on issue 181 by [email protected]: 4 billion seconds added to
expiry when system time steps backwards
http://code.google.com/p/memcached/issues/detail?id=181
Just made the clock monotonic for 1.4.7... Leaving a test instance running
for the next week or two to see how much drift there is off reality.
Tests seem to run okay so far. If the clock ends up being wildly inaccurate
I'll inline the clock_gettime() code, before 1.4.7-final.
People should really adjust clocks *before* starting daemons... but this
bug is common for other reasons as well.