Github messages for voidlinux
 help / color / mirror / Atom feed
From: LinArcX <LinArcX@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] My system clock is four minutes behind. How do I fix it?
Date: Fri, 26 Aug 2022 18:21:04 +0200	[thread overview]
Message-ID: <20220826162104.gzmvVSeniphOzW-S0D7cezfvL2Lnnq56LJo62_ejetU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38918@inbox.vuxu.org>

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

Closed issue by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38918

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.19_1 x86_64 GenuineIntel uptodate hold rFF

### Package(s) Affected

openntpd

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

When i login to my machine, it should report the correct time.log in

### Actual behaviour

It's 4 minutes behind. For example, if right now it is 14:20, my machine will show 14:16. I should manually restart openntpd service to fix this problem.

I'm using openntpd as "Network Time Protocol" implementation, but even switching to chrony has the same issue.

### Steps to reproduce

Just install openntpd and enable it's service.its

  parent reply	other threads:[~2022-08-26 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  8:41 [ISSUE] " LinArcX
2022-08-26 11:05 ` Anachron
2022-08-26 11:15 ` LinArcX
2022-08-26 11:16 ` LinArcX
2022-08-26 11:26 ` Anachron
2022-08-26 14:56 ` sgn
2022-08-26 16:21 ` LinArcX
2022-08-26 16:21 ` LinArcX [this message]
2022-08-26 16:22 ` LinArcX
2022-08-26 17:05 ` Duncaen
2022-08-26 17:05 ` Duncaen

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=20220826162104.gzmvVSeniphOzW-S0D7cezfvL2Lnnq56LJo62_ejetU@z \
    --to=linarcx@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).