Re: sntpclock: warning: unable to read clock: timed out

Hi Paul,

I'm sorry but that's not right.
In the system time is more than 2 "away" from the result that sntpclock
fetches you will get the error: "sntpclock: fatal: time uncertainty too
large"

Please see this example:

(current date)
# date
Tue Nov 12 19:17:16 CET 2002

(verify that sntpclock works)
# sntpclock 192.38.7.240 | clockview
before: 2002-11-12 19:17:34.487208000000000000
after:  2002-11-12 19:17:34.482176999902330338

(then change the date)
# date 111019102002
Sun Nov 10 19:10:00 CET 2002

(and run sntpclock again)
# sntpclock 192.38.7.240 | clockview
sntpclock: fatal: time uncertainty too large
clockview: fatal: data split across packets

(then change the date so that is it within the 2 days interval - current
time is now 19:18:50)
# date 111019202002
Sun Nov 10 19:20:00 CET 2002

(and run sntpclock again)
# sntpclock 192.38.7.240 | clockview
before: 2002-11-10 19:20:02.052874000000000000
after:  2002-11-12 19:19:58.966644499913759529



kind regards Uffe


----- Original Message -----
From: "Paul Jarc" <[email protected]>
To: <[email protected]>
Sent: Tuesday, November 12, 2002 7:09 PM
Subject: Re: sntpclock: warning: unable to read clock: timed out


> "Uffe Jakobsen" <[email protected]> wrote:
> > If your local clock differs from the sntpclock result by more than 2
days
> > sntpclock will fail
> > Propably with the mesg: "sntpclock: fatal: time uncertainty too
large"....
>
> No, that message means your network is too slow, so sntpclock can't
> pin down the difference between the local and remote clocks with
> enough precision.
>
>
> paul
>