> lockclock stays in OK
You need to think about what "stays in" means. Do you want to support it? If so, we need documentation and a test case. I will let somebody else take care of Issue #524 The simplest fix that I can think of is to change --enable-lockclock to something like --enable-lockclock-and-I-know-what-I'm-doing. Note that packaging/SUSE/ntpsec.spec includes --enable-lockclock Looks like they enabled everything. I wonder if anybody tried that recipe. If I understand what happens, ntpd won't work as either a client or server on a normal system. It will run, but won't do anything useful unless you configure the local driver and have some back door mechanism disciplining the system clock. (But maybe they did try it and it does work. I've been wrong before, but see #524) Plan B would be to add a run time trap. You can catch the simple case of not configuring the local clock, but I don't know how to catch the case where the local clock is configured but there is nothing actually disciplining the system clock. Plan C would be to make it a run time option so a distro could ship a version configured with everything so it would work in the normal case and also work in the lockclock mode with a new line in ntp.conf -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
