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 >
