On Thursday 09 August 2018 10:19:46 Fred wrote: > Hi, > > Someone complained off list about the timestamp in my emails being > off. Being a hardware person I think hardware should work properly and > clocks should keep accurate time. So I installed ntpdate as suggested > but it is not active yet.
And it only sets the clock once, at boot time. > Todays version of ntp(ntpd) handles that right well, my hardware clock is on grenwich and software on local, and both stay within 50 milliseconds of real time. > If I ask google what time it is in Mesa AZ. the response agrees > closely with an "atomic" clock I have. The computer clock is about 10 > min. fast. > > fred@ragnok:~$ /usr/sbin/ntpdate -q time.nist.gov > server 2610:20:6f96:96::4, stratum 1, offset -610.512368, delay > 0.09421 server 132.163.96.4, stratum 1, offset -610.509394, delay > 0.08899 9 Aug 06:51:15 ntpdate[13672]: step time server 132.163.96.4 > offset -610.509394 sec > > fred@ragnok:~$ date > Thu Aug 9 06:51:18 MST 2018 > > The time server is quite close to the computer clock. What causes the > discrepancy? The offset in the time server response is about 10 min. > The offset is measured from what to what and how is it measured? > As stated. ntp handles that by making small corrections so as to not disturb other time sensitive stuff on your computer. Thats another way of saying your 10 minute error may take it 4 hours to correct. The hdwe clock is set as part of the shutdown, so if you don't run 24/7, you don't start from square one the next time you powerup. And its so little cpu load you may not even find it with some of the monitoring facilities. Here, sorted on cpu usage, its about the 20th down the htop list. > Best regards, > Fred -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
