I searched through all of the old messages on this subject and
couldn't find a fix for the problem, except using another time
server.
My problem is I'm behind a firewall and can only use a local
time server that won't work with rdate. Has rdate been fixed
yet? If so, is there somewhere can I
On Fri, 11 Feb 2000, Larry Fletcher wrote:
I searched through all of the old messages on this subject and
couldn't find a fix for the problem, except using another time
server.
My problem is I'm behind a firewall and can only use a local
time server that won't work with rdate. Has rdate
It's working now:
# rdate time.nist.gov
Sat Jan 1 20:12:01 2000
On Sat, Jan 01, 2000 at 05:06:59PM -, Pollywog wrote:
On 01-Jan-2000 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
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 ---
On 01-Jan-2000 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
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
On Sat, Jan 01, 2000 at 11:51, Ben Collins wrote:
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
7 matches
Mail list logo