Comment #1 on issue 389 by [email protected]: internal clock drift from
system time
https://code.google.com/p/memcached/issues/detail?id=389
Yeah that does happen.
The primary motivator for doing that was for people *with* ntpd though. On
boot their clock would be weird, and memcached and ntpd would both start at
similar times. Then ntpd would do a large initial correction and the daemon
would be goofed until restart.
This happened pretty often, and switching it to use ntpd also requires that
you make it start after the clock is corrected.
Going to leave this open and see if we can do the time slew thing.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
