> On 21 Jul 2023, at 05:31, Tim via users wrote:
>
> There are difficulties in Windows handling the
> hardware clock set to UTC
I have been dual booting fedora and windows 10/11 for a very long time.
there are no issues with the bios clock being in utc i have every encountered.
Barry
__
On Thu, 2023-07-20 at 22:15 -0400, Jeffrey Walton wrote:
> > My main point was about during installation. There used to be a
> > very
> > obvious checkbox for hardware clock is set to UTC. I don't recall
> > that
> > being the case for a long time.
>
> I think Tim is correct. There used to be a
On Thu, 2023-07-20 at 22:15 -0400, Jeffrey Walton wrote:
> I think Tim is correct. There used to be a checkbox about the hardware
> clock. (Maybe it is still there?)
If it is, I don't think it was obvious. I don't recall seeing it for a
long time.
> But I don't think the user is to blame. Users
On Thu, Jul 20, 2023 at 8:41 PM Tim via users
wrote:
>
> Tim:
> >> I seem to remember it used to be quite straight-forward to set up a
> >> new installation with the clock set to UTC. Now it's far less
> >> obvious how its been configured, and to tell it to do what you want.
>
> Patrick O'Callagh
Tim:
>> I seem to remember it used to be quite straight-forward to set up a
>> new installation with the clock set to UTC. Now it's far less
>> obvious how its been configured, and to tell it to do what you want.
Patrick O'Callaghan:
> To check, just run 'timedatectl' with no arguments:
>
> $ ti
On Thu, 2023-07-20 at 22:19 +0930, Tim via users wrote:
> On Thu, 2023-07-20 at 10:51 +0100, Patrick O'Callaghan wrote:
> > Not a bug, just user error (my own). Turns out my hardware clock
> > was
> > set to local time, which is not recommended. The fix:
> >
> > # timedatectl set-local-rtc 0
>
>
On Thu, 2023-07-20 at 10:51 +0100, Patrick O'Callaghan wrote:
> Not a bug, just user error (my own). Turns out my hardware clock was
> set to local time, which is not recommended. The fix:
>
> # timedatectl set-local-rtc 0
I seem to remember it used to be quite straight-forward to set up a new
in
On Mon, 2023-07-17 at 12:20 +0100, Patrick O'Callaghan wrote:
> My system hibernates and powers down at 1:30am, and is woken up by a
> smart plug powering it on at 8am. This is working (touch wood) and
> the
> system verifiably wakes up at 8am. However the journal logs of the
> resume event show 9a
On Tue, 2023-07-18 at 06:09 +0100, Barry wrote:
>
>
> > On 17 Jul 2023, at 22:15, Patrick O'Callaghan
> > wrote:
> >
> > That would imply that either all entries are shifted, or none are,
> > which is not what I observe.
>
> You have confirmed that the system powers on at 08:00 BST.
> But the
> On 17 Jul 2023, at 22:15, Patrick O'Callaghan wrote:
>
> That would imply that either all entries are shifted, or none are,
> which is not what I observe.
You have confirmed that the system powers on at 08:00 BST.
But the logs are for 09:00 when you view them with journalctl for events while
On Mon, 2023-07-17 at 17:57 +0100, Barry wrote:
>
>
> > On 17 Jul 2023, at 13:46, George N. White III
> > wrote:
> >
> > I see something similar. I assume the system starts on hardware
> > clock time, then
> > after file systems are up the localtime data are used.
>
> Journal entries are all
> On 17 Jul 2023, at 13:46, George N. White III wrote:
>
> I see something similar. I assume the system starts on hardware clock time,
> then
> after file systems are up the localtime data are used.
Journal entries are all utc and local time is applied only on display with
journalctl is my
On Mon, 2023-07-17 at 09:45 -0300, George N. White III wrote:
> On Mon, Jul 17, 2023 at 8:21 AM Patrick O'Callaghan
>
> wrote:
>
> > My system hibernates and powers down at 1:30am, and is woken up by
> > a
> > smart plug powering it on at 8am. This is working (touch wood) and
> > the
> > system v
On Mon, Jul 17, 2023 at 8:21 AM Patrick O'Callaghan
wrote:
> My system hibernates and powers down at 1:30am, and is woken up by a
> smart plug powering it on at 8am. This is working (touch wood) and the
> system verifiably wakes up at 8am. However the journal logs of the
> resume event show 9am,
My system hibernates and powers down at 1:30am, and is woken up by a
smart plug powering it on at 8am. This is working (touch wood) and the
system verifiably wakes up at 8am. However the journal logs of the
resume event show 9am, even though once fully resumed the time is
correct. The difference wo
15 matches
Mail list logo
