|
|
Posted by Michael Fesser on 06/24/07 16:37
..oO(Jerry Stuckle)
>It depends on a lot of things. Many systems do not have the necessary
>hardware adjust clock speed.
It can all be done and corrected with software.
>So just like any clock, if it's running
>fast, it must be set back sooner or later.
Not necessarily. On my local server:
kira:~# date; hwclock
So 24. Jun 18:24:39 CEST 2007
So 24 Jun 2007 18:24:09 CEST -0.758366 Sekunden
The system clock is synchronized with an NTP server, while the hardware
RTC is half a minute behind. It simply doesn't matter. The RTC is only
used to maintain the time when the system is down, the system clock is
controlled by software and is always as exact as possible.
If there would be a real difference between the system clock and the
"real time", my local NTP daemon (chrony) would slightly speed up or
slow down the system clock, so after a short period of time it would be
in sync again without any gaps or "time jumps".
Micha
Navigation:
[Reply to this message]
|