On 11/18/18 1:22 PM, Stephen Morris wrote: > On 16/11/18 12:17 pm, Rick Stevens wrote: >> On 11/15/18 4:54 PM, Ed Greshko wrote: >>> On 11/16/18 7:37 AM, Rick Stevens wrote: >>>> On 11/15/18 3:00 PM, Joe Zeff wrote: >>>>> On 11/15/2018 03:17 PM, Rick Stevens wrote: >>>>>> In Linux >>>>>> case, it expects UTC. In Windows, it expects local time. >>>>> I haven't had to deal with this for years, but if memory serves, >>>>> there's >>>>> a place where you can tell Linux that the hardware clock is in local >>>>> time, not UTC. >>>> Ah, yes, there is. You can select the mode when you install the system, >>>> but the "system-config-date" utility offers a tickbox. By default, it's >>>> ticked and that means "System clock uses UTC". >>>> >>>> I also haven't done it in a while. This machine is F28, but started >>>> life as F18 and has been continually updated since then. The same is >>>> true for my other personal systems (they're current F28 or F29 and >>>> started as F20 or earlier). For the last 25 years or so, 95% of the >>>> machines I set up or use are Unix-esque in flavor, so I pretty much >>>> always set up UTC on the hardware clock. Sort of second nature. >>> Well, I'm just installing an F29 MATE VM and on the TIME&DATE screen >>> there is no tick-box >>> to indicate that the HW clock is or isn't "local". >>> >>> Additionally, I could find no trace of "system-config-date" in F29. >>> >>> [root@meimei ~]# dnf whatprovides *bin/system-config-date >>> Fedora 29 - x86_64 - VirtualBox 2.8 kB/s | 6.9 >>> kB 00:02 >>> Failed to synchronize cache for repo 'virtualbox', ignoring this repo. >>> Error: No Matches found >> And you're right. It appears mine is from....(holy kapok!) F24! I told >> you these machines have been updated from older versions. >> >> Ok, so you can wait until chronyd syncs, then delete the /etc/adjtime >> file and "sudo hwclock -w --utc" to set it to UTC (default unless the >> last line of /etc/adjtime is set to "LOCAL"). > > I've checked my etc/adjtime and it has the last line set to local. I > also can't see anything obvious in that file to indicate the offset from > local to GMT so how does hwclock know what offset to use? Ok, so Fedora thinks your HW clock is in local time, so when your system is booted, your system clock is also in local time. Eventually, chronyd or some other NTP client will change your system clock (NOT your hardware clock) to UTC. As to the data contained in the adjtime file, do "man hwclock" and look at the "The Adjtime File" section. As to your timezone offsets and such, that is in the timezone data. There is a symlink, /etc/localtime, that should point to the actual timezone data file. In my case: /etc/localtime -> /usr/share/zoneinfo/America/Los_Angeles That's where the offsets, daylight saving time, whatever is kept. > Also when I issue the hwclock command, it tells me my timezone is > GMT+11, which is correct for daylight savings time. Given that I can't > find any setting in KDE->System Settings any more to tell Fedora to > allow for daylight savings time, and noting that the hwclock is correct > for local daylight savings time, nor can I find any settings to specify > a Network Time Clock any more that would adjust the time accordingly, > how is my clocks correct for daylight savings time, or is the fact that > I'm tri-booting with windows causing the clocks to be correct? Keep in mind that your _hardware_ clock is NOT the same as your _system_ clock. Your hardware clock runs all by itself on the motherboard, generally off a crystal controlled oscillator and powered by that coin battery on the mobo. It is used to set the _system_ clock to the current time at boot. The kernel and apps depend on the _system_ clock and expect it to be in UTC. Chronyd/NTP affect the _system_ clock. Now, depending on your settings, at shutdown you can have the system clock reset your hardware clock so it will be updated to the correct time as updated by chronyd (useful if the hardware clock drifts...and a lot of them do). That's why that "UTC" or "LOCAL" is in /etc/adjtime...so the hwclock tool knows what to do if it's told to update the hardware clock. > I've done a check for system-config-date and it doesn't exist on my F28 > system either, but then I did in the past have to re-install F26 from > scratch, so that may have removed it. >From what I gather, they stopped including it in F26. Don't know why... it's a pretty useful tool. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - When you don't know what to do, walk fast and look worried. - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
