Re: rdate fails Y2K?
On Sat, Jan 01, 2000 at 08:35:10AM -0800, Pann McCuaig wrote:
> # ping time.nist.gov
> PING time.nist.gov (192.43.244.18): 56 data bytes
> 64 bytes from 192.43.244.18: icmp_seq=0 ttl=47 time=85.3 ms
> 64 bytes from 192.43.244.18: icmp_seq=1 ttl=47 time=92.2 ms
>
> --- time.nist.gov ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max = 85.3/88.7/92.2 ms
>
> # rdate -p time.nist.gov
> rdate: Could not read data: No such file or directory
After looking at the source, it seems that either time.nist.gov was
returning too much data, or none at all. Note, this worked when I used my
ISP's local Solaris time server, so this isn't a problem in rdate itself,
it has something to do with the time.nist.gov server. Now after checking,
it seems that it is returning more data than rdate expects.
--
-----------=======-=-======-=========-----------=====------------=-=------
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` bcollins@debian.org - collinbm@djj.state.va.us - bmc@visi.net '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
Reply to: