| Re: [chrony-users] Simple DHCP support |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
William G. Unruh __| Canadian Institute for|____ Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _|____ Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology |____ unruh@xxxxxxxxxxxxxx
Canada V6T 1Z1 ____|____ and Gravity ______|_ theory.physics.ubc.ca/
On Fri, 9 Aug 2024, Jan Claußen wrote:
[CAUTION: Non-UBC Email]Because I have a system that is not connected to the internet at all times. My main
server is connected at times and syncs to a public NTP server. This main server then servers the time to many
clients, which should be able to discover the local NTP server via DHCP. systemd-timesyncd did this without
Why do they need to discover it? You know it. You can code it into
chrony.conf. Surely that server IP does not change from day to day, and if it
did, your machines which are up for 100 days at a time, would not know it from
the DHCP they ran 100 days ago.
the need for any configuration. I thought since chrony is so sophisticated, it could easily add such a feature
as well without the need for any scripting.
You do know that chrony is opensource, and you can always add this feature if
it is so important to you, and it is so easy to do?
The RTC is not supposed to be a reliable time source to better than hours.
Note that my dhcp does not deliver ntp sources.
Also, your system clock after it is disciplined by ntpd or chrony is a far
better time source than is the RTC even after many hours.