Alex Perry wrote:
hardware clock). Once the clock is close, by using this method, the ntp
will always be able to keep it on time from then onwards.
Agreed.
To check if ntp is in a happy state, use the 'ntpq -p' command.
ntpq -p
Look for low fractional jitter numbers and low offset
On Sun, 2004-11-14 at 12:05 -0700, Bob Proulx wrote:
Alex Perry wrote:
hardware clock). Once the clock is close, by using this method, the ntp
will always be able to keep it on time from then onwards.
Agreed.
To check if ntp is in a happy state, use the 'ntpq -p' command.
ntpq -p
I think it's best not to install package adjtimex along ntp as they try to do
the same thing (keep the system on time).
ntp server will indeed no set the time if it's way off. However, Setting the
time to a wild approximation (+/- 1 hour) of the current time is usually
enough for ntp to
The debian package ntpdate has the purpose of initializing the clock
to a sane value on boot (so it is even usable on machines with a broken
hardware clock). Once the clock is close, by using this method, the ntp
will always be able to keep it on time from then onwards.
If you're concerned
OK, so if your system clock is way off and NTP doesn't work, try this
before blaming hardware:
1) delete /etc/adjtime
2) run /etc/init.d/hwclock.sh
3) run adjtimexconfig
4) run ntpdate server
5) run /etc/init.d/ntp-server start
Turns out my adjtime was way off due to a bad clock on the previous
5 matches
Mail list logo
