Jone <yeger9@gmail.com> writes:

>> I guess this explains the wrong timestamps of your e-mails! :)
>
> Previously, did not pay attention, but wrong time in system log is
> extremely undesirable.
>
>> You can fix it with `hwclock --systohc`
>
> .. and no changes. ??

Currently, Guix/GuixSD will not set your hardware clock.  How is Guix
supposed to know what time it is?  This is one of those things, like
disk partitioning, that falls outside of the "functional bubble" in
which Guix lives.  You need to set the hardware clock yourself.  The
system clock will be set by ntpd if it is running.

For more information on the difference between the hardware clock and
the system clock, see "Clocks in a Linux System" in "man hwclock".

Jone <yeger9@gmail.com> writes:

>> sudo herd status ntpd
>
> Status of ntpd:
>   It is started.
>   Running value is 14818.
>   It is enabled.
>   Provides (ntpd).
>   Requires (user-processes networking).
>   Conflicts with ().
>   Will be respawned.

I wonder if there are any errors in your system log related to ntpd?
According to "man ntpd": "Normally, ntpd exits with a message to the
system log if the offset exceeds the panic threshold, which is 1000 s by
default."

-- 
Chris