From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: chrony: fix wrong option in the default config.
Date: Wed, 30 Oct 2019 15:56:28 +0100 [thread overview]
Message-ID: <20191030145628.1gM2SeIc7oXQONi0yt7l7JP-0bqln88u7z1XuyEpnrY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15936@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
There's a merged pull request on the void-packages repository
chrony: fix wrong option in the default config.
https://github.com/void-linux/void-packages/pull/15936
Description:
The option rtcfile in the default config conflicts with runit's stage 3.
Chronyd in RTC mode takes control of /dev/rtc to measure RTC drift.
Stage 3 calls hwclock -w, which messes up chrony's drift calculation.
Furthermore the current chronyd runit service needs the -s option
to effectively use the RTC feature.
See for more info:
https://chrony.tuxfamily.org/faq.html#_i_want_to_use_code_chronyd_code_s_rtc_support_must_i_disable_code_hwclock_code
Switch rtcfile to the rtcsync option, to be consistent with stage 3.
Example config file 1 sets the right options that work out of the box.
So use that example file instead of editing the annotated one.
Example config file 3 will instead be installed to /usr/share/examples.
prev parent reply other threads:[~2019-10-30 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 7:24 [PR PATCH] " voidlinux-github
2019-10-30 7:40 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-30 7:40 ` voidlinux-github
2019-10-30 7:43 ` voidlinux-github
2019-10-30 7:43 ` voidlinux-github
2019-10-30 14:56 ` voidlinux-github [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=20191030145628.1gM2SeIc7oXQONi0yt7l7JP-0bqln88u7z1XuyEpnrY@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).