mouz <email address hidden> writes:
> By 'the problem is not present' I mean the following:
> - prepare a KVM guest with the wanted release
> - install the ntp package on the guest
> - set the clock a minute backwards on the guest
> - force the network to change using the DHCP server on the KVM host
> - observe ntpd listening on the new address (can take a few minutes)
> - observe the time being synchronized
The ntp daemon will not learn that it is supposed to aim at different
NTP servers, so it doesn't matter that it is listening on the new
address. I do not observe the time re-synchronizing itself under these
circumstances. In fact, I observe it getting significantly off, which
is quite irritating and the reason I figured out there was a problem
in the first place.
mouz <email address hidden> writes:
> By 'the problem is not present' I mean the following:
> - prepare a KVM guest with the wanted release
> - install the ntp package on the guest
> - set the clock a minute backwards on the guest
> - force the network to change using the DHCP server on the KVM host
> - observe ntpd listening on the new address (can take a few minutes)
> - observe the time being synchronized
The ntp daemon will not learn that it is supposed to aim at different
NTP servers, so it doesn't matter that it is listening on the new
address. I do not observe the time re-synchronizing itself under these
circumstances. In fact, I observe it getting significantly off, which
is quite irritating and the reason I figured out there was a problem
in the first place.
Perry
--
Perry E. Metzger <email address hidden>