In article <[email protected]>, david-
[email protected] says...
>
> It seems that, on Windows at least, ntpq -crv gives results in local time,
> and not in UTC. Is that intended? Is there a switch for results in UTC?
>
> ntp 4.2.7p265
>
> Thanks,
> David
Same on my FreeBSD 8.0 box. That's showing local time, not UTC.
[g0wbx@FBSD ~]$ ntpq -crv
assID=0 status=24f4 leap_none, sync_uhf_clock/PPS, 15 events,
event_peer/strat_chg,
version="ntpd 4.2.4p5-a (1)", processor="i386",
system="FreeBSD/8.0-RELEASE", leap=00, stratum=1, precision=-19,
rootdelay=0.000, rootdispersion=0.303, peer=65385, refid=GPS,
reftime=d32fcf9f.9afd6e44 Wed, Apr 11 2012 10:38:39.605, poll=4,
clock=d32fcfa4.040a9f90 Wed, Apr 11 2012 10:38:44.015, state=4,
offset=0.002, frequency=97.389, jitter=0.002, noise=0.004,
stability=0.005, tai=0
Yes I know it's all old version stuff now, but it all seems to keep
ticking along OK.
The software that needs the NTP service takes care of the UTC/Local
difference itself as needed.
("Faros", from http://www.dxatlas.com/Faros/)
relevant contents of ntp.conf
# GPS on /dev/gps1 (first serial port)
server 127.127.20.1 mode 0 minpoll 4 maxpoll 4 prefer
fudge 127.127.20.1 flag1 1 flag3 1 refid GPS
No other NTP sources intentionaly, my web connection (Demon UK) has too
wild a variation of ping latency for NTP to work reliably, whoever's
servers I use. It keeps far better time with no other external
reference when the GPS burps, than if I let it "see" other servers.
Thankfully, the GPS hasn't "burped" for well over a year now.
(Me and my mouth....)
and fyi:
[g0wbx@FBSD /etc]$ uptime
10:47AM up 296 days, 21:34, 1 user, load averages: 0.00, 0.00, 0.00
It doesnt get a lot of use! ;-) That uptime is from the last "dust-
bunny clearout" session.
Regards.
Dave B (G0WBX)
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
