On 11/15/18 2:40 PM, Ed Greshko wrote: > On 11/16/18 6:17 AM, Rick Stevens wrote: >> On 11/15/18 2:00 PM, Ed Greshko wrote: >>> On 11/16/18 4:50 AM, Stephen Morris wrote: >>>> On 14/11/18 8:46 am, Ed Greshko wrote: >>>>> On 11/14/18 5:32 AM, Stephen Morris wrote: >>>>>> My hardware clock is running a couple of seconds slow as well. >>>>>> >>>>>> Just as a matter of curiosity, when you say if you issue hwclock from the bios (how have >>>>>> you done that) what does journalctl show for the same time? Does it show, using your >>>>>> example, 2018-11-12 21:47 or does it show 2018-11-13 21:47? >>>>> I did not say what you think I said. >>>>> >>>>> I said, "But if I reboot and go into the BIOS it will show 2018-11-12 21:47", which I >>>>> thought was clear. >>>>> >>>>> To expound. I reboot, enter F2 when the Boot (not grub) splash screen comes up and enter >>>>> the BIOS setup of the motherboard. >>>> I've checked my bios and the bios home screen shows the date and time as local time (I >>>> also don't remember seeing any functionality on any bios screen to change that. I have >>>> had motherboards in the past that have provided that functionality.). >>> There must be a way to change it since someone must have set it at some point in time. >>> >>> Until you get it set to GMT/UTC you're going to have strange times in your logs. >> The vast majority of motherboards I've seen don't have a timezone >> setting on them, just a date and time and it's up to you to sort out >> what GMT/UTC is relative to your local time and enter it (the UTC data) >> appropriately. > > Maybe there is a disconnect on wording. > > Yes, none of the BIOS on my systems have a TimeZone setting. > > What I'm trying to say is that when you are in the BIOS screen the Date/Time should be > that of GMT/UTC and not local. Yes, that's what I'm saying. _YOU_ have to sort out what the correct UTC is and enter it. The firmware (BIOS/UEFI) has no way of doing the offset for you unless it has a timezone setting as well (most that I've seen don't), so it's a manual job. > I've never seen a BIOS that didn't have a way to change Date/Time. But, if so, what is > below should work for him. > >> I guess alternately, you could wait for cronyd or whatever to sync the >> system clock to UTC, then use "sudo hwclock -w" to set the hardware >> clock from the system clock. The journal and everything is based on >> the system clock, which is what cronyd "pokes". The hardware clock is >> just there to give the system clock a starting point at boot. In Linux >> case, it expects UTC. In Windows, it expects local time. >> > > I also don't dual boot, VM's work for me, but I seem to remember when you have your system > set up as Linux would like it then Windows has fits. :-) :-) Yup. > Coffee, I need Coffee! Me, too! Black. And strong! If you don't have to chew, it ain't strong enough! ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Warning: You are logged into reality as the root user... - ---------------------------------------------------------------------- _______________________________________________ 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
