void-linux / void-linux/void-docs
Missing "how to manually adjust the date" section on the date-time page
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 217
- Forks
- 212
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
https://docs.voidlinux.org/config/date-time.html
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 `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
Certificate verification failed for /C=US/O=Let's Encrypt/CN=R3
SSL_connect returned 1
ERROR: [reposync] failed to fetch file `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata': 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 `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the date-time page at docs.voidlinux.org/config/date-time.html and review the reported date/date --set transcript. Add a manual date-setting example and address the question about whether dhcpcd uses DHCP option 42 for a local NTP server, then verify the rendered documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100