On Mon, Jul 18, 2016 at 11:27:09PM +0300, Andrew Savchenko wrote > > As I wrote earlier in this thread, ntp server is not a guarantee > that such problems will not happen. If hardware clocked was > significantly offset during boot, it may take several _hours_ for > ntp to fix this via clock skew. Apparantly commit may be made > during these several hours.
I'm amazed that "robust linux servers" are deathly afraid of simply setting the time, and being done with it. And while we're at it, if a developer is doing development on a server machine, he may have other problems to worry about. At home I occasionally manually run a script that includes the 2 lines... /usr/bin/sudo /usr/bin/openrdate -n -s ca.pool.ntp.org /usr/bin/sudo /sbin/hwclock --systohc -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
