|Re: [chrony-users] Fwd: Chrony malfunctioning at beaglebones|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On 05/10/2015 10:38, Nuno Gonçalves wrote:
On Mon, Oct 5, 2015 at 10:31 AM, Tomalak Geret'kal <tom@xxxxxxxxx> wrote:
Timezone changes don't (shouldn't!) change the time. Timezone settings
(including DST offsets) are applied when generating a human-readable
timestamp, but do not affect the actual clock.
chronyd assumes by default that the real time clock (RTC) keeps local
time (including any daylight saving changes). This is convenient on
PCs running Linux which are dual-booted with DOS or Windows.
NOTE : IF YOU KEEP THE REAL TIME CLOCK ON LOCAL TIME AND YOUR COMPUTER
IS OFF WHEN DAYLIGHT SAVING (SUMMER TIME) STARTS OR ENDS, THE
COMPUTER’S SYSTEM TIME WILL BE ONE HOUR IN ERROR WHEN YOU NEXT BOOT
AND START CHRONYD.
An alternative is for the RTC to keep Universal Coordinated Time
(UTC). This does not suffer from the 1 hour problem when daylight
saving starts or ends.
If the rtconutc directive appears, it means the RTC is required to
keep UTC. The directive takes no arguments. It is equivalent to
specifying the -u switch to the Linux ‘/sbin/hwclock’ program.
Note that this setting is overriden when the hwclockfile directive
(see section hwclockfile) is used.
Okay that's .... weird.
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.