Re: Mystry of ntpdate
From: Juha Laiho (Juha.Laiho_at_iki.fi)
Date: 01/20/04
- Next message: Raymond Chui: "Re: Mystry of ntpdate"
- Previous message: RC: "Re: Time adjustement"
- In reply to: RC: "Mystry of ntpdate"
- Next in thread: Raymond Chui: "Re: Mystry of ntpdate"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 20 Jan 2004 20:07:00 GMT
[followups limited to comp.unix.admin]
RC <raymond.chui@noaa.gov> said:
>I have two Redhat Linux 7.2 sit next to each other.
>When I issued the command by root
>
>/usr/sbin/ntpdate ntp2.usno.navy.mil
>
>One machine I got
>
>20 Jan 13:54:01 ntpdate[19985]: step time server 192.5.41.209 offset
>0.992795 sec
>
>That's great!! But other machine I got
>
>20 Jan 13:48:36 ntpdate[23867]: no server suitable for synchronization found
>
>Why is that?
Might be that ntpdate doesn't want to jump the time more than some
limited value (5 mins or so). So, on the other machine the clock must
first be manually adjusted to closer to the correct time.
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)
- Next message: Raymond Chui: "Re: Mystry of ntpdate"
- Previous message: RC: "Re: Time adjustement"
- In reply to: RC: "Mystry of ntpdate"
- Next in thread: Raymond Chui: "Re: Mystry of ntpdate"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
