CentOS - Feb 2015 - Why the command 'service ntpd stop' cause the time reversed?

I've seen situations where people have put ntpdate in a cronjob to get
around issues with big time jumps at boot or dodgy clocks under
virtualization. There are much better solutions to this problem, so
let us know if this is the case for you.

K

On 2/11/2015 11:47 PM, Kahlil Hodgson wrote:
> I've seen situations where people have put ntpdate in a cronjob to get
> around issues with big time jumps at boot or dodgy clocks under
> virtualization. There are much better solutions to this problem, so
> let us know if this is the case for you.
NOT compatible with running ntpd!!!



-- 
john r pierce                                      37N 122W
somewhere on the middle of the left coast

> I've seen situations where people have put ntpdate in a cronjob to get
> around issues with big time jumps at boot or dodgy clocks under
> virtualization. There are much better solutions to this problem, so
> let us know if this is the case for you.
>
put "tinker panic 0" in your ntp.conf.

This stops ntpd from throwing a wobbly if it sees large jumps in time and
will keep clocks in virtualised environments ticking along.

Hi guys,
I don't use virtual machine.
The 192.168.0.191 is an internal ntpd server configured by administrator,  so i
can not see what  ntp server it synchronizes to or what is its time reference.
But i have added a new line "server 192.168.0.191" into file
"/etc/ntp.conf" on ntpd client machines, and the output to execute
command ntpstat is as follows:
synchronised to NTP server (192.168.0.191) at stratum 3
   time correct to within 80 ms
   polling server every 128 s


Is it an proper way to synchronize clock?