[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: using clock2.redhat.com with ntpd causes failure
- From: Harry Putnam <reader newsguy com>
- To: fedora-test-list redhat com
- Subject: Re: using clock2.redhat.com with ntpd causes failure
- Date: Mon, 12 Apr 2004 22:16:09 -0500
"Charles R. Anderson" <cra WPI EDU> writes:
> On Sat, Apr 10, 2004 at 01:59:06PM -0500, Harry Putnam wrote:
>> I was under the impression that clock2.redhat.com was usable for ntpd.
>> But a little test with rdate shows the possible source of failure:
>>
>> rdate -p clock2.redhat.com
>> Alarm clock
>
> rdate does not talk NTP. Try ntpdate (while ntpd is not running).
# ntpdate -q clock2.redhat.com
Looking for host clock2.redhat.com and service ntp
host found : clock3.redhat.com
server 209.132.176.4, stratum 0, offset 0.000000, delay 0.00000
12 Apr 22:15:17 ntpdate[12261]: no server suitable for synchronization found
Are you able to synchronize on clock2?
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]