-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2005-12-16 at 03:10 -0500, Carl Hartung wrote:
4. When the above process is completed, the client is effectively synced to the server. This makes two things possible: a) the hardware clock drift can be accurately measured and, b) that drift can be compensated for in software until the hardware clock is due for it's next adjustment (cron job? reboot?)
The hardware clock, aka CMOS clock, is only adjusted during boot by the script /etc/init.d/boot.clock, using a calculated value from /etc/adjtime; it is not touched again. The drift is calculated during the halt procedure by the same script. The ntp daemon does not touches nor adjusts the hardware, aka CMOS, clock, but only the system clock. - From /usr/share/doc/packages/xntp-doc/NTP-FAQ/NTP-s-trouble.htm: |> 8.3.1.1.2. How can I set the CMOS clock? |> |> Basically ntpd only sets the system time of the operating system. |> Therefore setting the CMOS clock is the responsibility of the operating |> system and its associated tools. To make things worse, typical PC |> operating systems and the BIOS set the RTC to local time, while |> UNIX-like operating systems set the RTC to UTC. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDo0d9tTMYHG2NR9URAmVqAJ4+gD76QFu6CFkkAPRgyZ+dMUrruACgkBwL 3V1DaSBFVctP/zGialp9YVQ= =8RCw -----END PGP SIGNATURE-----