I was going to respond to your pull request on github, I just had other things to do earlier.
On Thu, Mar 21, 2024 at 12:18:02PM +0000, Andy Fiddaman wrote: > There is a bootstrapping problem, however. If the system comes up without > external connectivity, then the two boundary servers authoritatively > advertise 1986 at stratum 10. There are also several other scenarios we've > encountered that can occur depending on the state of connectivity. > > This patch adds two new options to "local" to help in these situations. > > The first, "local oncesynced" prevents the local reference being activated > unless time was synchronised at some point in the past. This makes sense to me, although I think it might be better to generalize it as an activating root distance, which would completement the distance option (threshold). > The second, "local mintime" prevents the local reference being activated > unless the system clock is later than the specified time. Can you please explain why both options are needed? This seems more like a hack, that should have a better solution than making assumptions about absolute time. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
