On Thu, 10 Jan 2013 09:25:03 -0800 darx@sent.com wrote:
I have/use a Roaming Laptop (Opensuse 12.2/KDE) that connects to a variety of networks, with varying assigned IPs, frequently offline.
It's a very common use-case.
For network managemet, I use NetworkManager.
I need to manage clock-sync, conditionally using different servers depending on LAN/IP state. E.g.,
(1) @ local only / offline, use NO server, local clock only (2) @ LAN ip = specific IP (e.g., @ my office LAN, 10.11.12.13), use ntp server = 10.11.12.100 (3) @ a roaming-assigned, random IP, use a set of external/public stratum servers.
Opensuse 12.2/Factory 'officially' package/release ntpd.
I currently launch ntpd with a systemd unit file.
Conditional ntp config could be implemented by building logic into
(1) systemd unit (2) NetworkManager up/down/change scripts
Discussing upstream @ both 'systemd' and 'ntp', neither is recommended. From both, for such roaming use cases, the use of "chrony" (http://chrony.tuxfamily.org/FAQ.html#question_2.1) is recommended. Particularly as ntpd sync/slew is not reliable if the host machine is often disconnected.
Checking opensuse* for chrony packaging, I find we do NOT package it for 12.2 at all, and for -factory there's no official release, only in network:time.
For such a frequent/common use case, I'm requesting that chrony be considered for promotion/inclusion as an official product, and enabled for both factory and current stable release.
See: https://build.opensuse.org/request/show/147993 Note it needs to be accepted by the maintainers of network:time. Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org