From: bcookatpcsd <bcookatpcsd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: incorrect date on hwclock.. no ntp client in base..
Date: Thu, 18 Mar 2021 14:14:30 +0100 [thread overview]
Message-ID: <20210318131430.TuULgX0jEovOPN1s0hrKdpRMSisu-SAGJfK_JiCfbAE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29513@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]
New comment by bcookatpcsd on void-packages repository
https://github.com/void-linux/void-packages/issues/29513#issuecomment-801916803
Comment:
Great, I'll try that on the next one..
I'd still suggest getting "how to manually adjust the date" section to the Date-Time page in the docs..
```
[I] root@Void63 ~# hwclock -v
hwclock from util-linux 2.36.2
System Time: 1616073138.456523
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2018/07/01 08:48:28
Hw clock time : 2018/07/01 08:48:28 = 1530434908 seconds since 1969
Time since last adjustment is 1530434908 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-07-01 04:48:27.436904-04:00
[I] root@Void63 ~# chronyc sources
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^+ time1.google.com 1 10 377 600 -222us[ -474us] +/- 12ms
^* time4.google.com 1 10 377 520 -313us[ -567us] +/- 9640us
^+ time3.google.com 1 10 377 609 -998us[-1251us] +/- 10ms
^+ time2.google.com 1 10 377 701 -654us[ -905us] +/- 12ms
^+ time.cloudflare.com 3 10 377 581 -616us[ -869us] +/- 7837us
^+ time.cloudflare.com 3 10 377 658 -57us[ -309us] +/- 7904us
[I] root@Void63 ~# hwclock -w
[I] root@Void63 ~# hwclock -v
hwclock from util-linux 2.36.2
System Time: 1616073197.256809
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1616073193 seconds after 1969
Last calibration done at 1616073193 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2021/03/18 13:13:18
Hw clock time : 2021/03/18 13:13:18 = 1616073198 seconds since 1969
Time since last adjustment is 5 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2021-03-18 09:13:17.249374-04:00
```
prev parent reply other threads:[~2021-03-18 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 18:18 [ISSUE] " bcookatpcsd
2021-03-18 6:36 ` Anachron
2021-03-18 13:14 ` bcookatpcsd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210318131430.TuULgX0jEovOPN1s0hrKdpRMSisu-SAGJfK_JiCfbAE@z \
--to=bcookatpcsd@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).