On 25/04/13 23:07, Nick Khamis wrote:
>> Ummm... *all* servers are critically time-sensitive.
>>
>
> Yeah... I concur ;)
>
Define critical! - to my mind if its critical you should be running your
own atomic clock, and something like a pps system to distribute it ...
or somewhere in the middle a local gps receiver for time lock.
Or do you mean reasonably accurate, but closely synced local systems?
My interest after having a stable ntp based hierarchy for years is in
trying to get the same using a cisco router and VMs' - not easy so far!
When I used an ancient netgear adsl, and a linux firewall/ntp server it
was very good, now ...
Does anyone know a good guide to using time sync in VM's, for both
windows and linux (gentoo) guests using libvirt? Especially for guests
that are resumed, or the whole virtualisation system is hibernated? (ntp
refuses to resync after guest pause/save/restore/resume (known problem),
even with "tinker panic 0"
My current setup is complicated by using a cisco router (adsl) as the
localnet master via local (ISP/University) time servers - its rather
inaccurate so while the machines are often "locked", its in rather
relative terms :)
ghost#sh ntp ass
address ref clock st when poll reach delay offset
disp
+~130.95.128.36 210.9.192.50 2 44 64 377 11.9 -844.4
213.6
+~116.66.162.4 130.234.255.83 2 8 64 377 48.7 -907.5
213.3
+~203.0.178.191 43.128.117.84 2 23 64 377 12.2 -891.0
213.3
~192.168.48.1 134.115.4.33 3 9h39 64 0 17.3 -616.8
16000.
*~27.54.95.11 218.100.43.70 2 42 64 377 12.7 -846.7
221.4
+~202.127.210.36 223.255.185.2 2 31 64 377 62.2 -845.3
211.2
+~130.102.128.23 132.163.4.101 2 38 64 377 77.3 -850.4
212.4
* master (synced), # master (unsynced), + selected, - candidate, ~
configured
ghost#
asterisk ~ # ntpq -p
remote refid st t when poll reach delay offset
jitter
==============================================================================
ghost.lan.local 27.54.95.11 3 u 64 64 377 1.386 2838.19
513.843
asterisk
