Referring to http://tf.nist.gov/timefreq/service/its.htm
For your basic needs: Pipe literal |tcpclient nist1.symmetricom.com 13 oneresponse|xlate a2e| cons 55139 09-11-04 21:09:38 00 0 0 0.0 UTC(NIST) * Ready; T=0.01/0.01 13:09:37 That's a left-coast server. Depending on where you are you might choose a wrong-coast one, Or try several ;-) There's a link on the referenced page to servers. -- Mike Harding z/VM System Support [email protected] [email protected] [email protected] (925) 926-3179 (w) (925) 457-9183 (c) IM: VMBearDad (AIM), mbhcpcvt (Y!) CMSTSO Pipelines Discussion List <[email protected]> wrote on 11/03/2009 06:54:49 AM: > From: Bob Cronin <[email protected]> > To: [email protected] > Date: 11/03/2009 06:55 AM > Subject: Re: Using PIPE to obtain the GMT time from an ntp server? > Sent by: CMSTSO Pipelines Discussion List <[email protected]> > > Our VM clocks are so far off that I wouldn't even care if the answer I got > from the ntp server was a few seconds off because of latency... > -- > bc > > On Tue, Nov 3, 2009 at 2:21 AM, Rob van der Heij <[email protected]> wrote: > > > On Mon, Nov 2, 2009 at 10:50 PM, Paul Gilmartin <[email protected]> > > wrote: > > > > > Is there a stage that talks to OpenEdition CMS? (I have _no_ > > > experience with OpenEdition CMS.) If so, all that's necessary > > > is to capture the output of "TZ=GMT0 date". > > > > > > (In TSO it's easy enough with "address SYSCALL".) > > > > This is cheating. Sure, if you assume the operating system has the > > right time, you just ask there... > > > > A pipeline to encode and decode the NTP packets should not be that > > hard. But even with a pipeline that can handle those you probably > > still need to follow the protocol that does several requests to > > eliminate the effect of network latency. This is why the ntp client > > takes a while to "stabilize" before it adjusts the OS correction > > factors. > > > > Rob > >
