$ sudo ntpdate -d 172.18.100.168 10 Nov 10:07:57 ntpdate[5892]: ntpdate 4.2.6p5@1.2349-o Wed Oct 9 18:57:00 UTC 2013 (1) Looking for host 172.18.100.168 and service ntp host found : 172.18.100.168 transmit(172.18.100.168) receive(172.18.100.168) transmit(172.18.100.168) receive(172.18.100.168) transmit(172.18.100.168) receive(172.18.100.168) transmit(172.18.100.168) receive(172.18.100.168) 172.18.100.168: Server dropped: server is very broken server 172.18.100.168, port 123 stratum 9, precision -21, leap 00, trust 000 refid [172.18.100.168], delay 0.02631, dispersion 0.00000 transmitted 4, in filter 4 reference time: d80a9c4a.02281b8f Mon, Nov 10 2014 10:07:06.008 originate timestamp: d8096562.75139fc6 Sun, Nov 9 2014 12:00:34.457 transmit timestamp: d80a9c83.eee02d38 Mon, Nov 10 2014 10:08:03.933 filter delay: 0.02631 0.02634 0.02664 0.02635 0.00000 0.00000 0.00000 0.00000 filter offset: -79649.4 -79649.4 -79649.4 -79649.4 0.000000 0.000000 0.000000 0.000000 delay 0.02631, dispersion 0.00000 offset -79649.476483
10 Nov 10:08:03 ntpdate[5892]: no server suitable for synchronization found
但有时候服务器时间比客户端时间大,也是可以的,这类问题比较奇怪。下面是成功的例子:
1 2 3 4 5 6 7 8
# date 01091100 Thu Jan 9 11:00:00 GMT-8 2014 # ntpdate -u 172.18.100.168 Looking for host 172.18.100.168 and service ntp host found : 172.18.100.168 9 Nov 12:01:49 ntpdate[626]: step time server 172.18.100.168 offset 26269305.872492 sec # date Sun Nov 9 12:01:50 GMT-8 2014
而有时候,国内的服务器却似段公子的六脉神剑,时灵时不灵,下面是一个例子:
1 2 3 4 5 6 7 8 9 10 11 12
# date 11091200 Sun Nov 9 12:00:00 CST 2014 root@localhost:~# ntpdate -u 202.120.2.101 9 Nov 12:02:28 ntpdate[2607]: no server suitable for synchronization found root@localhost:~# ntpdate -u 202.120.2.101 9 Nov 12:02:39 ntpdate[2608]: no server suitable for synchronization found root@localhost:~# root@localhost:~# root@localhost:~# ntpdate -u 133.100.11.8 10 Nov 10:29:22 ntpdate[2628]: step time server 133.100.11.8 offset 80736.496480 sec root@localhost:~# date Mon Nov 10 10:29:24 CST 2014