Am 17.11.18 um 19:47 schrieb Stefan Brüns:
On Samstag, 17. November 2018 19:34:53 CET Stefan Seyfried wrote:
No. ntp-refclock *reuses* hardware drivers distributed as part of ntp and makes them work standalone. It is a very tiny part of ntp.
OK, and then I need a "ntp-broadcast" deamon in addition to chrony to use broadcast / multicast ntp etc.,
Chrony can broadcast. I does not listen to broadcasts, see https:// chrony.tuxfamily.org/ faq.html#_can_code_chronyd_code_be_driven_from_broadcast_multicast_ntp_servers for the reasoning.
How many clients do you have in your network? 10.000? 100.000?
about 20, but ntp broadcast is just an easy no-configuration-needed setup that I'm using now since about 15 years. But yes, changing this to e.g. dhcp based config would be a solution. For most of the clients probably also systemd-timesyncd would be good enough, but my "maschine-schoen.sh" script that runs after installation definitely would need changing ;-)
Or is this just a strawman? Using a GPS PPS clock and broadcast mode is contradicting ...
It's a DCF77 serial port receiver, and it worked beautifully with broadcast. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org