Github messages for voidlinux
 help / color / mirror / Atom feed
From: bcookatpcsd <>
Subject: [ISSUE] incorrect date on hwclock.. no ntp client in base..
Date: Tue, 16 Mar 2021 19:18:45 +0100	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

New issue by bcookatpcsd on void-packages repository


Does not have any example how to fix the date and time on a system with incorrect date and time.. 

xpbs-install -S chrony wouldn't work because the ssl cert was so far in the future.. 

Can we get an example of, 

To set the date on a local system, where the local date and time is very out of sync..

date --set="20210316 14:10"

The would set the date to March 16th, 2021 and it is 2:10pm.

(then I could do xbps-install.. chrony.. etc..)

[root@voidME ~]# xbps-install -S chrony rsync 
[*] Updating repository `' ...
Certificate verification failed for /C=US/O=Let's Encrypt/CN=R3
SSL_connect returned 1
ERROR: [reposync] failed to fetch file `': Operation not permitted
[root@voidME ~]# ntpdate
bash: ntpdate: command not found
[root@voidME ~]# date
Thu Jun 28 11:37:47 EDT 2018
[root@voidME ~]# date --set="20210316 14:10"
Tue Mar 16 14:10:00 EDT 2021
[root@voidME ~]# date
Tue Mar 16 14:10:01 EDT 2021
[root@voidME ~]# xbps-install -S chrony rsync 
[*] Updating repository `' ...
x86_64-musl-repodata: 1646KB [avg rate: 18MB/s]


Also, my local network exports an ntp server and is running locally.. does the dhcpcd client not look for option 42?

             reply	other threads:[~2021-03-16 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 18:18 bcookatpcsd [this message]
2021-03-18  6:36 ` Anachron
2021-03-18 13:14 ` bcookatpcsd

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).