On 01-Jan-2000 Ben Collins wrote: > 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.
I entered 'rdate -s lilypad' from my laptop and it worked, so I also don't believe rdate is the problem. I also had a problem with an update from time.nist.gov. -- Andrew
