lockclock runtime option

[Eric S. Raymond]

Achim Gratz via devel <devel at ntpsec.org>:
> Eric S. Raymond via devel writes:
> > I have converted ENABLE_LOCKCLOCK to a runtime option. Following a
> > review suggestion, it is controlled by flag1 of the localclock driver.
> 
> With the condition bug out of the way, I have a more fundamental problem
> with the "runtime" part of that patch.
> 
> In principle you can mobilize/demobilize associations and change their
> flags at runtime (I haven't done that in a while so I don't know if it
> still works the same as in classic).  So if I need to convince myself
> that all the initializations are going to happen correctly when
> lockclock is switched on and off, I really don't see how I'd go about
> that.

I don't either, and I think there is no functional point in trying to cope
with that. So I'm going to deal with this by adding to the documentation a
line that says changing this flag at runtime may produce undefined behavior.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.