get current drift value - comp.protocols.time.ntp

April wrote: > is there a way to get the current drift value, using ntp utilities > such as ntpq and ntpdc, instead of opening the ntp.drift file? ntpq -c rv This command returns a lot of info: C:\>ntpq -c rv associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer, version="ntpd 4.2.7p132@1.2478-o Feb 23 13:55:41 (UTC+01:00) 2011 (1)", processor="x86", system="Windows", leap=00, stratum=2, precision=-19, rootdelay=0.952, rootdisp=24.321, refid=241.10.116.86, reftime=d117d2f5.dc257ff4 Tue, Mar 1 2011 21:17:57.859, clock=d117d4ee.e17a6898 Tue, Mar 1 2011 21:26:22.880, peer=58961, tc=6, mintc=3, offset=-6.749, frequency=5.941, sys_jitter=59.553, clk_jitter=8.906, clk_wander=0.153, ctr_frequency=-5.13 Near the end you'll notice 'frequency=5.941' which is the current drift value! Terje -- - <Terje.Mathisen at tmsw.no> "almost all programming can be viewed as an exercise in caching"

On Mar 1, 3:28=A0pm, Terje Mathisen <"terje.mathisen at tmsw.no"> wrote: > April wrote: > > is there a way to get the current drift value, using ntp utilities > > such as ntpq and ntpdc, instead of opening the ntp.drift file? > > ntpq -c rv > > This command returns a lot of info: > > C:\>ntpq -c rv > associd=3D0 status=3D0618 leap_none, sync_ntp, 1 event, no_sys_peer, > version=3D"ntpd 4.2.7p...@1.2478-o Feb 23 13:55:41 (UTC+01:00) 2011 =A0(1= )", > processor=3D"x86", system=3D"Windows", leap=3D00, stratum=3D2, precision= =3D-19, > rootdelay=3D0.952, rootdisp=3D24.321, refid=3D241.10.116.86, > reftime=3Dd117d2f5.dc257ff4 =A0Tue, Mar =A01 2011 21:17:57.859, > clock=3Dd117d4ee.e17a6898 =A0Tue, Mar =A01 2011 21:26:22.880, peer=3D5896= 1, tc=3D6, > mintc=3D3, offset=3D-6.749, frequency=3D5.941, sys_jitter=3D59.553, > clk_jitter=3D8.906, clk_wander=3D0.153, ctr_frequency=3D-5.13 > > Near the end you'll notice 'frequency=3D5.941' which is the current drift > value! > > Terje > > -- > - <Terje.Mathisen at tmsw.no> > "almost all programming can be viewed as an exercise in caching" Thanks Terje! I have an ntp v3 server and the output value looks like ppb (instead of ppm). Also tried ntpdc -c loopinfo which can auto adjust and get back the values of ppm for both v3 and v4. :-) April

On 2011-03-01, April <xiaoxia2005a@yahoo.com> wrote: > On Mar 1, 3:28?pm, Terje Mathisen <"terje.mathisen at tmsw.no"> wrote: >> April wrote: >> > is there a way to get the current drift value, using ntp utilities >> > such as ntpq and ntpdc, instead of opening the ntp.drift file? >> >> ntpq -c rv >> >> This command returns a lot of info: >> >> C:\>ntpq -c rv >> associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer, >> version="ntpd 4.2.7p...@1.2478-o Feb 23 13:55:41 (UTC+01:00) 2011 ?(1)", >> processor="x86", system="Windows", leap=00, stratum=2, precision=-19, >> rootdelay=0.952, rootdisp=24.321, refid=241.10.116.86, >> reftime=d117d2f5.dc257ff4 ?Tue, Mar ?1 2011 21:17:57.859, >> clock=d117d4ee.e17a6898 ?Tue, Mar ?1 2011 21:26:22.880, peer=58961, tc=6, >> mintc=3, offset=-6.749, frequency=5.941, sys_jitter=59.553, >> clk_jitter=8.906, clk_wander=0.153, ctr_frequency=-5.13 >> >> Near the end you'll notice 'frequency=5.941' which is the current drift >> value! >> >> Terje >> >> -- >> - <Terje.Mathisen at tmsw.no> >> "almost all programming can be viewed as an exercise in caching" > > Thanks Terje! I have an ntp v3 server and the output value looks like > ppb (instead of ppm). Why not tell us what it says, rather than your interpretation. AFAIK it has always been ppm. Also tried ntpdc -c loopinfo which can auto > adjust and get back the values of ppm for both v3 and v4. :-) April

On Mar 1, 7:39=A0pm, unruh <un...@wormhole.physics.ubc.ca> wrote: > On 2011-03-01, April <xiaoxia20...@yahoo.com> wrote: > > > > > > > > > On Mar 1, 3:28?pm, Terje Mathisen <"terje.mathisen at tmsw.no"> wrote: > >> April wrote: > >> > is there a way to get the current drift value, using ntp utilities > >> > such as ntpq and ntpdc, instead of opening the ntp.drift file? > > >> ntpq -c rv > > >> This command returns a lot of info: > > >> C:\>ntpq -c rv > >> associd=3D0 status=3D0618 leap_none, sync_ntp, 1 event, no_sys_peer, > >> version=3D"ntpd 4.2.7p...@1.2478-o Feb 23 13:55:41 (UTC+01:00) 2011 ?(= 1)", > >> processor=3D"x86", system=3D"Windows", leap=3D00, stratum=3D2, precisi= on=3D-19, > >> rootdelay=3D0.952, rootdisp=3D24.321, refid=3D241.10.116.86, > >> reftime=3Dd117d2f5.dc257ff4 ?Tue, Mar ?1 2011 21:17:57.859, > >> clock=3Dd117d4ee.e17a6898 ?Tue, Mar ?1 2011 21:26:22.880, peer=3D58961= , tc=3D6, > >> mintc=3D3, offset=3D-6.749, frequency=3D5.941, sys_jitter=3D59.553, > >> clk_jitter=3D8.906, clk_wander=3D0.153, ctr_frequency=3D-5.13 > > >> Near the end you'll notice 'frequency=3D5.941' which is the current dr= ift > >> value! > > >> Terje > > >> -- > >> - <Terje.Mathisen at tmsw.no> > >> "almost all programming can be viewed as an exercise in caching" > > > Thanks Terje! =A0I have an ntp v3 server and the output value looks lik= e > > ppb (instead of ppm). > > Why not tell us what it says, rather than your interpretation. AFAIK it > has always been ppm. > > =A0Also tried ntpdc -c loopinfo which can auto > > > > > > > > > adjust and get back the values of ppm for both v3 and v4. :-) =A0April # ntpq -c rv xxx.xxx.xxx.xxx assID=3D0 status=3D06f4 leap_none, sync_ntp, 15 events, event_peer/ strat_chg, system=3D"SunOS", leap=3D00, stratum=3D2, rootdelay=3D0.600, rootdispersion=3D10.440, peer=3D26941, refid=3D171.201.3.126, reftime=3Dd117e7bb.69219000 Tue, Mar 1 2011 21:46:35.410, poll=3D10, clock=3Dd117e973.5ad00000 Tue, Mar 1 2011 21:53:55.354, phase=3D-0.033, freq=3D37218.31, error=3D2.55 # ntpdc -c loopinfo xxx.xxx.xxx.xxx ***Warning changing to older implementation ***Warning changing the request packet size from 160 to 48 offset: -0.000033 s frequency: 37.218 ppm poll adjust: 30 watchdog timer: 491 s

On Mar 1, 7:39=A0pm, unruh <un...@wormhole.physics.ubc.ca> wrote: > On 2011-03-01, April <xiaoxia20...@yahoo.com> wrote: > > > > > > > > > On Mar 1, 3:28?pm, Terje Mathisen <"terje.mathisen at tmsw.no"> wrote: > >> April wrote: > >> > is there a way to get the current drift value, using ntp utilities > >> > such as ntpq and ntpdc, instead of opening the ntp.drift file? > > >> ntpq -c rv > > >> This command returns a lot of info: > > >> C:\>ntpq -c rv > >> associd=3D0 status=3D0618 leap_none, sync_ntp, 1 event, no_sys_peer, > >> version=3D"ntpd 4.2.7p...@1.2478-o Feb 23 13:55:41 (UTC+01:00) 2011 ?(= 1)", > >> processor=3D"x86", system=3D"Windows", leap=3D00, stratum=3D2, precisi= on=3D-19, > >> rootdelay=3D0.952, rootdisp=3D24.321, refid=3D241.10.116.86, > >> reftime=3Dd117d2f5.dc257ff4 ?Tue, Mar ?1 2011 21:17:57.859, > >> clock=3Dd117d4ee.e17a6898 ?Tue, Mar ?1 2011 21:26:22.880, peer=3D58961= , tc=3D6, > >> mintc=3D3, offset=3D-6.749, frequency=3D5.941, sys_jitter=3D59.553, > >> clk_jitter=3D8.906, clk_wander=3D0.153, ctr_frequency=3D-5.13 > > >> Near the end you'll notice 'frequency=3D5.941' which is the current dr= ift > >> value! > > >> Terje > > >> -- > >> - <Terje.Mathisen at tmsw.no> > >> "almost all programming can be viewed as an exercise in caching" > > > Thanks Terje! =A0I have an ntp v3 server and the output value looks lik= e > > ppb (instead of ppm). > > Why not tell us what it says, rather than your interpretation. AFAIK it > has always been ppm. > > =A0Also tried ntpdc -c loopinfo which can auto > > > > > > > > > adjust and get back the values of ppm for both v3 and v4. :-) =A0April # ntpq -c rv xxx.xxx.xxx.xxx assID=3D0 status=3D06f4 leap_none, sync_ntp, 15 events, event_peer/ strat_chg, system=3D"SunOS", leap=3D00, stratum=3D2, rootdelay=3D0.600, rootdispersion=3D10.440, peer=3D26941, refid=3Dxxx.xxx.xxx.xxx, reftime=3Dd117e7bb.69219000 Tue, Mar 1 2011 21:46:35.410, poll=3D10, clock=3Dd117e973.5ad00000 Tue, Mar 1 2011 21:53:55.354, phase=3D-0.033, freq=3D37218.31, error=3D2.55 # ntpdc -c loopinfo xxx.xxx.xxx.xxx ***Warning changing to older implementation ***Warning changing the request packet size from 160 to 48 offset: -0.000033 s frequency: 37.218 ppm poll adjust: 30 watchdog timer: 491 s

Similiar Articles:

get current drift value - comp.protocols.time.ntp
is there a way to get the current drift value, using ntp utilities such as ntpq and ntpdc, instead of opening the ntp.drift file? ...

calculating drift value for ntp.drift? - comp.protocols.time.ntp ...
Utility to measure time drift - comp.protocols.time.ntp get current drift value - comp.protocols.time.ntp is there a way to get the current drift value, using ntp ...

Utility to measure time drift - comp.protocols.time.ntp
get current drift value - comp.protocols.time.ntp Utility to measure time drift - comp.protocols.time.ntp get current drift value - comp.protocols.time.ntp is there a way ...

Removing a Drifting Baseline - comp.soft-sys.matlab
get current drift value - comp.protocols.time.ntp Removing a Drifting Baseline - comp.soft-sys.matlab get current drift value - comp.protocols.time.ntp Removing a Drifting ...

ntp.drift - comp.protocols.time.ntp
get current drift value - comp.protocols.time.ntp is there a way to get the current drift value, using ntp utilities such as ntpq and ntpdc, instead of opening the ntp ...

ntpd vs ntpq!!!!! - comp.protocols.time.ntp
hello everybody, i have a serious problem while running ntpd-4.2.4p4. while i type ntpd -D 3 it says wildcard interface #0 0.0.0.0 disabled.is this w...

Watchdog timer - comp.arch.embedded
get current drift value - comp.protocols.time.ntp... Warning changing the request packet size from 160 to 48 offset: -0.000033 s frequency: 37.218 ppm poll adjust: 30 ...

Solairs 8 xntpd client oscillates - comp.protocols.time.ntp ...
You may have a bogus drift value in the kernel and in the drift ... The daemon would call the "get current time" routine, and in the guts, the clock value read would be ...

still not able to get NTP to sync on windows 7 even w/ more ...
Interestingly, the > drift file values on win7 do not get written out for a long time, > after ... It shows just how much better the 4.2.4 version was than the current ...

ntpd, boot time, and hot plugging - comp.protocols.time.ntp ...
In the current design compromise, a server is ... wondered why ntpd would throw a valuable drift value ... Stratum 1 timeserver, and without a good drift file, you can get ...

get current drift value - comp.protocols.time.ntp | Computer Group
is there a way to get the current drift value, using ntp utilities such as ntpq and ntpdc, instead of opening the ntp.drift file? ...

Electric current - Wikipedia, the free encyclopedia
Electric current is a flow of electric charge through a medium. This charge is ... This phrase is frequently used when discussing the value of an electric current ...

7/15/2012 7:42:11 PM