search for: 258254

...re details. > The NTP configuration option you may be after is "tinker panic 0" which allows NTP to make big jumps as often as required. See ntp_misc(5). There is a related discussion with making VMs take big jumps at https://www.centos.org/forums/viewtopic.php?f=16&t=61186&p=258254#p258254 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20170205/5cad9399/attachment-0001.sig>

...t; The NTP configuration option you may be after is "tinker panic 0" which > allows NTP to make big jumps as often as required. See ntp_misc(5). > There is a related discussion with making VMs take big jumps at > https://www.centos.org/forums/viewtopic.php?f=16&t=61186&p=258254#p258254 Thanks. I will look at this. All I was seeing was to use burst and iburst, but they would not make the really big jump needed after boot.

> Date: Sunday, February 05, 2017 10:26:05 -0500 > From: Robert Moskowitz <rgm at htt-consult.com> > > I have read: > http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet > ween-ntpd-and-chronyd/ > > My server is up all the time and will serve time to internal > systems (via DHCP options). > > Caveat is that my server is an armv7

I have read: http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-between-ntpd-and-chronyd/ My server is up all the time and will serve time to internal systems (via DHCP options). Caveat is that my server is an armv7 (Cubieboard2) which does not have an RTC (no battery). So whenever the system boots, the time is ZERO (Dec 31, 1969 or some such). Chrony fixes this really fast;