Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chrony: fix wrong option in the default config. #15936

Merged
merged 1 commit into from
Oct 30, 2019

Conversation

travankor
Copy link
Contributor

@travankor travankor commented Oct 30, 2019

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.

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.
@Hoshpak Hoshpak merged commit 713d884 into void-linux:master Oct 30, 2019
@travankor travankor deleted the chrony branch October 31, 2019 08:26
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants