https://marvelvsdc.faith/index.php?title=Linux_Obtaining_the_Correct_Time&feed=atom&action=historyLinux Obtaining the Correct Time - Revision history2024-03-28T19:46:27ZRevision history for this page on the wikiMediaWiki 1.30.0https://marvelvsdc.faith/index.php?title=Linux_Obtaining_the_Correct_Time&diff=955086&oldid=prevHahnbooth2 at 01:45, 20 April 20212021-04-20T01:45:19Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr style="vertical-align: top;" lang="en">
<td colspan="2" style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: white; color:black; text-align: center;">Revision as of 01:45, 20 April 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Ensuring a computer <del class="diffchange diffchange-inline">isn't just </del>displaying the right time but that it<del class="diffchange diffchange-inline">'s </del>being maintained accurately is not as straight-forward <del class="diffchange diffchange-inline">since </del>it first sounds.<br /><br />Most Linux systems have two clocks. The hardware clock, <del class="diffchange diffchange-inline">generally </del>known as the CMOS of Bios clock, is <del class="diffchange diffchange-inline">usually </del>a simple crystal oscillator with battery back-up that maintains time <del class="diffchange diffchange-inline">when </del>your system is off or boots up. <del class="diffchange diffchange-inline">This clock </del>is <del class="diffchange diffchange-inline">usually </del>located on the motherboard and will run on a regular basis, however these clock chips tend to lose time <del class="diffchange diffchange-inline">as </del>the computer ages and the battery weakens.<br /><br />The other clock, the machine clock, is a software clock and it starts <del class="diffchange diffchange-inline">once </del>you boot up one's body often getting <del class="diffchange diffchange-inline">a first </del>time from the hardware clock. System clocks keep time <del class="diffchange diffchange-inline">with the addition of </del>seconds to a prime epoch, a base time that for Linux and Unix, began at <del class="diffchange diffchange-inline">midnight </del>on January 1, 1970.<br /><br />However, the hardware clock is a cheap electronic oscillator and cannot maintain time and energy to any useful degree of accuracy. They often drift several seconds <del class="diffchange diffchange-inline">a </del>day which for day-to-day process is <del class="diffchange diffchange-inline">most likely </del>adequate but as time passes sensitive applications it could cause serious problems.<br /><br /><del class="diffchange diffchange-inline">A better way </del>is to set the system clock using the time from <del class="diffchange diffchange-inline">a </del>NTP (Network Time Protocol) time server. <del class="diffchange diffchange-inline">These </del>dedicated time servers get yourself a UTC (Coordinated Universal Time) time from an atomic clock which will be the most accurate time keepers <del class="diffchange diffchange-inline">on earth</del>, not losing a second <del class="diffchange diffchange-inline">in </del>time in several millions of years.<br /><br />Dedicated NTP servers use either a radio receiver to pick-up a radio time and frequency broadcast which are transmitted by several national laboratories or utilizing the timing signal broadcast from the GPS network.<br /><br />Linux uses a NTP service called NTP Daemon (ntpd). This uses NTP to <del class="diffchange diffchange-inline">regulate </del>the system clock for just about any drift in time <del class="diffchange diffchange-inline">as </del>it frequently check the UTC time source.<br /><br />To configure the NTP daemon the ntp.conf file in the /etc directory <del class="diffchange diffchange-inline">may </del>be used. From here more than one time server may be used as a reference <del class="diffchange diffchange-inline">plus </del>the frequency it is checked can be altered.</div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Ensuring a computer <ins class="diffchange diffchange-inline">is not only </ins>displaying the right time but that it <ins class="diffchange diffchange-inline">is </ins>being maintained accurately is not as straight-forward <ins class="diffchange diffchange-inline">as </ins>it first sounds.<br /><br />Most Linux systems have two clocks. The hardware clock, <ins class="diffchange diffchange-inline">also </ins>known as the CMOS of Bios clock, is <ins class="diffchange diffchange-inline">generally </ins>a simple crystal oscillator with battery back-up that maintains time <ins class="diffchange diffchange-inline">whenever </ins>your system is off or boots up. <ins class="diffchange diffchange-inline">[http://www.pearltrees.com/mccrackenhahn3 more info] </ins>is <ins class="diffchange diffchange-inline">normally </ins>located on the motherboard and will run on a regular basis, however these clock chips tend to lose time <ins class="diffchange diffchange-inline">because </ins>the computer ages and the battery weakens.<br /><br />The other clock, the machine clock, is <ins class="diffchange diffchange-inline">really </ins>a software clock and it starts <ins class="diffchange diffchange-inline">when </ins>you boot up one's body often getting <ins class="diffchange diffchange-inline">an initial </ins>time from the hardware clock. System clocks keep time <ins class="diffchange diffchange-inline">by adding </ins>seconds to a prime epoch, a base time that for Linux and Unix, began at <ins class="diffchange diffchange-inline">nighttime </ins>on January 1, 1970.<br /><br />However, the hardware clock is a cheap electronic oscillator and cannot maintain time and energy to any useful degree of accuracy. They often drift several seconds <ins class="diffchange diffchange-inline">each </ins>day which for day-to-day process is <ins class="diffchange diffchange-inline">probably </ins>adequate but as time passes sensitive applications it could cause serious problems.<br /><br /> <ins class="diffchange diffchange-inline">[https://slashdot.org/submission/13651580/linux---getting-the-correct-time check here] </ins>is to set the system clock using the time from <ins class="diffchange diffchange-inline">the </ins>NTP (Network Time Protocol) time server. <ins class="diffchange diffchange-inline">[https://www.instapaper.com/p/rushmathiassen5 website] </ins>dedicated time servers get yourself a UTC (Coordinated Universal Time) time from an atomic clock which will be the most accurate time keepers <ins class="diffchange diffchange-inline">in the world</ins>, not losing a second <ins class="diffchange diffchange-inline">with </ins>time in several millions of years.<br /><br />Dedicated NTP servers use either a radio receiver to pick-up a radio time and frequency broadcast which are transmitted by several national laboratories or utilizing the timing signal broadcast from the GPS network.<br /><br />Linux uses a NTP service called NTP Daemon (ntpd). This uses NTP to <ins class="diffchange diffchange-inline">adjust </ins>the system clock for just about any drift in time <ins class="diffchange diffchange-inline">since </ins>it frequently check the UTC time source.<br /><br />To configure the NTP daemon the ntp.conf file in the /etc directory <ins class="diffchange diffchange-inline">can </ins>be used. From here more than one time server may be used as a reference <ins class="diffchange diffchange-inline">and also </ins>the frequency it is checked can be altered.</div></td></tr>
</table>Hahnbooth2https://marvelvsdc.faith/index.php?title=Linux_Obtaining_the_Correct_Time&diff=955047&oldid=prevHahnbooth2: Created page with "Ensuring a computer isn't just displaying the right time but that it's being maintained accurately is not as straight-forward since it first sounds.<br /><br />Most Linux syst..."2021-04-20T01:26:44Z<p>Created page with "Ensuring a computer isn't just displaying the right time but that it's being maintained accurately is not as straight-forward since it first sounds.<br /><br />Most Linux syst..."</p>
<p><b>New page</b></p><div>Ensuring a computer isn't just displaying the right time but that it's being maintained accurately is not as straight-forward since it first sounds.<br /><br />Most Linux systems have two clocks. The hardware clock, generally known as the CMOS of Bios clock, is usually a simple crystal oscillator with battery back-up that maintains time when your system is off or boots up. This clock is usually located on the motherboard and will run on a regular basis, however these clock chips tend to lose time as the computer ages and the battery weakens.<br /><br />The other clock, the machine clock, is a software clock and it starts once you boot up one's body often getting a first time from the hardware clock. System clocks keep time with the addition of seconds to a prime epoch, a base time that for Linux and Unix, began at midnight on January 1, 1970.<br /><br />However, the hardware clock is a cheap electronic oscillator and cannot maintain time and energy to any useful degree of accuracy. They often drift several seconds a day which for day-to-day process is most likely adequate but as time passes sensitive applications it could cause serious problems.<br /><br />A better way is to set the system clock using the time from a NTP (Network Time Protocol) time server. These dedicated time servers get yourself a UTC (Coordinated Universal Time) time from an atomic clock which will be the most accurate time keepers on earth, not losing a second in time in several millions of years.<br /><br />Dedicated NTP servers use either a radio receiver to pick-up a radio time and frequency broadcast which are transmitted by several national laboratories or utilizing the timing signal broadcast from the GPS network.<br /><br />Linux uses a NTP service called NTP Daemon (ntpd). This uses NTP to regulate the system clock for just about any drift in time as it frequently check the UTC time source.<br /><br />To configure the NTP daemon the ntp.conf file in the /etc directory may be used. From here more than one time server may be used as a reference plus the frequency it is checked can be altered.</div>Hahnbooth2