Problems with linuxppc_2_4_devel

Gabriel Paubert paubert at
Wed Jan 16 22:39:58 EST 2002

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, even
if they don't go to full ntpd synchornisation. Besides that, the NTP
protocol is very simple, especially if you don't care about round trip
time measurement: it's UDP (on port 123 AFAIR).

> > b) see if the time is "too different" from the last changeset.  Most trees
> >    are fairly active and if the time is too far ahead (say a month?), then
> >    raise a warning and ask the user to confirm this is the correct time.
> I'd say 'b' with an override option (yes, the clock IS fine, the tree
> has just been dead for awhile).

Probably the best solution indeed...


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

More information about the Linuxppc-dev mailing list