[opensuse-factory] enabling ntpd or chrony by default?
Hello, on a recent Tumbleweed installation (new install on 2018-10-04) with the KDE default pattern, both ntpd and chrony get installed - but none of them get enabled by default :-( The (obvious) result is that the clock runs out of sync. Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-) Regards, Christian Boltz [1] The default chrony config seems to work - after simply starting it, I have a correct time again. -- There should be a send beer button somewhere in the bug tracker. [strahlex in https://github.com/openSUSE/software-o-o/issues/28] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2018-10-26 17:31, Christian Boltz wrote:
Hello,
on a recent Tumbleweed installation (new install on 2018-10-04) with the KDE default pattern, both ntpd and chrony get installed - but none of them get enabled by default :-(
The (obvious) result is that the clock runs out of sync.
Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-)
systemctl enable systemd-timesyncd (And do away with ntp and chrony? ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-)
systemctl enable systemd-timesyncd (And do away with ntp and chrony? ;-)
Irrespective of how and what he activates a time daemon - I do agree one of them should be activated by default during install. On the TW machine I installed two weeks ago chronyd *is* running, and I have not specifically done anything for that. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/26/2018 9:04 AM, Peter Suetterlin wrote:
Jan Engelhardt wrote:
Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-) systemctl enable systemd-timesyncd
Never heard of chrony until now. ntpd has been the reference implementation and is fairly mature/standard. What are the benefits of chrony other than it is new? Chrony appears to be able to operate in an "isolated manner" (off-network). Ntpd doesn't have that because it was designed for an "always connected" environment and the kernel has it's own subsystem for keeping local time consistent -- measuring drifts and applying corrections. The only downside of chrony was a lack of support for hardware clocks like GPS and other hardware-based time devices, vs. ntp coming with an assortment of drivers. That's not like a big deal for 99.99% of the users who don't have such HW. Unless a user needs HW support or has a HW clock to synchronize their time, chrony sounds like a better fit for opensuse (caveat -- this is based on my readings & research, not actual usage). -l -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Oct 31, 2018 at 10:30 AM L A Walsh
On 10/26/2018 9:04 AM, Peter Suetterlin wrote:
Jan Engelhardt wrote:
Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-) systemctl enable systemd-timesyncd
Never heard of chrony until now. ntpd has been the reference implementation and is fairly mature/standard. What are the benefits of chrony other than it is new?
It's not really so very new. We use chrony because it allows the time to be changed by a large amount at the very start. This is required in laptops or any computer that is powered on/off regularly. This is a critical feature in such systems. After time is initially set, chrony plays thhe gradual change game just like ntp. But if the initial startup is done this way, it can take eons before the time is correct. For a server that is always on, this is not so much of a concern.
Chrony appears to be able to operate in an "isolated manner" (off-network). Ntpd doesn't have that because it was designed for an "always connected" environment and the kernel has it's own subsystem for keeping local time consistent -- measuring drifts and applying corrections.
We use it off network in that the time information comes from a GPS. Our measurement systems are not in the internet.
The only downside of chrony was a lack of support for hardware clocks like GPS and other hardware-based time devices, vs. ntp coming with an assortment of drivers. That's not like a big deal for 99.99% of the users who don't have such HW.
We use chrony with gpsd as the source of time information. Our GPS are connected via a serial port and provide a PPS. So the time sync is very accurate. Also, chrony provides NTP services. So remote NTP clients are happy. A third contender will soon be the reimplemented NTP with, it is hoped, all the nasties in the current NTP implementation sorted: https://www.ntpsec.org/ -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 26.10.18 um 17:41 schrieb Jan Engelhardt:
On Friday 2018-10-26 17:31, Christian Boltz wrote:
Hello,
on a recent Tumbleweed installation (new install on 2018-10-04) with the KDE default pattern, both ntpd and chrony get installed - but none of them get enabled by default :-(
The (obvious) result is that the clock runs out of sync.
Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-)
systemctl enable systemd-timesyncd (And do away with ntp and chrony? ;-)
+1 That's what I do usually. Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On vendredi, 26 octobre 2018 20.30:51 h CEST Hendrik Woltersdorf wrote:
Am 26.10.18 um 17:41 schrieb Jan Engelhardt:
On Friday 2018-10-26 17:31, Christian Boltz wrote:
Hello,
on a recent Tumbleweed installation (new install on 2018-10-04) with the KDE default pattern, both ntpd and chrony get installed - but none of them get enabled by default :-(
The (obvious) result is that the clock runs out of sync.
Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-)
systemctl enable systemd-timesyncd (And do away with ntp and chrony? ;-)
+1
That's what I do usually.
Hendrik
I would say chronyd as local time server (you need one) and systemd-timesyncd pointing to that one first for all the rest of your ntp client in your network. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 27/10/2018 02:01, Christian Boltz wrote:
Hello,
on a recent Tumbleweed installation (new install on 2018-10-04) with the KDE default pattern, both ntpd and chrony get installed - but none of them get enabled by default :-(
The (obvious) result is that the clock runs out of sync.
Before I open a bugreport - what's the expected behaviour on a fresh installation? I'd vote for "enable chrony by default" [1] unless someone good reasons against that, or a better idea ;-)
This is probably worth 2 bug reports, 1. chrony should be started and 2. ntpd shouldn't be in a fresh install, it would be nice to know what recommends it, but it could just be that the pattern updates hadn't gone in yet. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Hello, Am Montag, 29. Oktober 2018, 00:01:26 CET schrieb Simon Lees:
This is probably worth 2 bug reports, 1. chrony should be started and
Reported as https://bugzilla.opensuse.org/show_bug.cgi?id=1113641
2. ntpd shouldn't be in a fresh install, it would be nice to know what recommends it, but it could just be that the pattern updates hadn't gone in yet.
# rpm -q --whatrecommends ntp patterns-yast-yast2_basis-20180613-1.1.x86_64 so s/hadn/haven/ ;-) Regards, Christian Boltz -- I know that. Please don't assume that I misunderstood you just because every systemd-basher during the last five years did the same thing. :-P [Matthias Urlichs in systemd-devel] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
V Mon, 29 Oct 2018 01:38:38 +0100
Christian Boltz
Hello,
Am Montag, 29. Oktober 2018, 00:01:26 CET schrieb Simon Lees:
This is probably worth 2 bug reports, 1. chrony should be started and
Reported as https://bugzilla.opensuse.org/show_bug.cgi?id=1113641
By default it should be started, but of course there is some conditions when it does not need to happen. Do not forget to attach yast logs to bug report.
2. ntpd shouldn't be in a fresh install, it would be nice to know what recommends it, but it could just be that the pattern updates hadn't gone in yet.
# rpm -q --whatrecommends ntp patterns-yast-yast2_basis-20180613-1.1.x86_64
so s/hadn/haven/ ;-)
This looks like result of some old bug. Now yast2 can configure chrony by default. https://github.com/yast/patterns-yast/blob/master/package/patterns-yast.spec... Josef
Regards,
Christian Boltz
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Bruno Friedmann -
Christian Boltz -
Hendrik Woltersdorf -
Jan Engelhardt -
Josef Reidinger -
L A Walsh -
Peter Suetterlin -
Roger Oberholtzer -
Simon Lees