Problems with linuxppc_2_4_devel

Gabriel Paubert paubert at
Thu Jan 17 05:43:39 EST 2002

On Wed, 16 Jan 2002, Tom Rini wrote:

> On Wed, Jan 16, 2002 at 12:39:58PM +0100, Gabriel Paubert wrote:
> >
> >
> > On Tue, 15 Jan 2002, Tom Rini wrote:
> >
> > > On Tue, Jan 15, 2002 at 01:02:03PM -0800, Larry McVoy wrote:
> > >
> > > > a) try and connect to a well known time server and see if the time is too
> > > >    far off at commit time.  May or may not work.
> > >
> > > This would require some external program tho, wouldn't it?
> >
> > It's called ntpq, and I believe most people should have it installed
> [snip]
> Should doesn't mean they will tho. :)  And the first time you assume
> everyone has something, 5 people pop up screaming 'cuz they don't.

No, but as I said, the protocol is trivial if you want a very approximate
time (use NTP v3 since all V4 servers I know support it). The problem is
finding the closest server, not sending an UDP packet and decoding the
answer and giving up if you don't receive anything after 5 packets or so.
I'm almost certain there is database of servers somewhere, but I just
don't remember where (between 2 cesium clocks, one hydrogen maser, 2 GPS
and one radio receiver I have enough references for my use at the
telescope ;-)). I also don't know whether some people could be blocked
from using NTP, but I don't think that it is a satisfactory solution in
any case.


** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list