Date: Fri, 25 Jul 1997 12:12:55 -0500 (CDT) From: David Kelly <dkelly@HiWAAY.net> To: brandon@roguetrader.com, dkelly@HiWAAY.net Cc: questions@FreeBSD.ORG Subject: Re: timedc, "ftp.apple.com will not tell us the date" Message-ID: <199707251712.MAA22866@fly.HiWAAY.net>
next in thread | raw e-mail | index | archive | help
Brandon Gillespie <brandon@roguetrader.com> replied:
>
> On Thu, 24 Jul 1997 dkelly@HiWAAY.net wrote:
> > timedc> c ftp.apple.com
> > ftp.apple.com will not tell us the date
> > time on ftp04.apple.com is 356793 ms. behind time on nexgen.hiwaay.net
> > timedc> c ftp.sgi.com
> > time on ftp.sgi.com is 34 ms. behind time on nexgen.hiwaay.net
> >
> > Why is it timedc insists a host will not tell it the date, then actually
> > reports it. Except: if the remote host is running SGI Irix, all is fine.
> > Same result from SGI to non-SGI host as shown above for FreeBSD to non-SGI.
>
> Just a guess, but 'ftp.apple.com' is simply used in a cluster lookup to
> multiple IP addresses, and is not actually an a-name for any specific IP,
> where ftp.cgi.com IS. Perhaps timedc is being a little more pedantic than
> it should about what address you are giving it?
My point was that timedc always takes extra time and reports the remote
host "will not tell us the date" if the remote host is NOT an SGI. I
just plucked ftp.apple.com out of the air as a non-SGI example, same
result for ftp.cdrom.com, or between any of my FreeBSD systems.
mdsc1: {101} timedc
timedc> c ftp.cdrom.com
ftp.cdrom.com will not tell us the date
time on wcarchive.cdrom.com is 7 ms. ahead of time on mdsc1
timedc>
FYI, mdsc1 is an SGI.
--
David Kelly N4HHE, dkelly@hiwaay.net (hm)
======================================================================
The human mind ordinarily operates at only ten percent of its
capacity -- the rest is overhead for the operating system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707251712.MAA22866>