WZZZ wrote:
So if the "updated ntp-restrict.conf and ntpd-wrapper that MI doesn't address" are retained in the system, as you suggest, from flatsixracer's rev4 that explains why those messages are still not generated, even after I overwrite the rev4 update using the MI build.
So next, maybe impossible to answer question, am I perhaps getting the best of both worlds by first installing the flatsix rev 4, which removes those messages, and then using the MI build, which uses binaries compiled by Xcode optimized for my CPU? (Or by simply editing those files myself).
Yes. I said the only difference between building your own and using flatsixracer installer is essentially those additional two files. Use his installer or install those two files yourself. The latter seems easier to me. Why use the installer just for those two files and then clobber all the rest with your own build? And frankly if you are using a 64-bit intel machine I don't know are gaining anything by building it yourself over using the installer. At the moment the only reason you might want to build it yourself is to build with the latest 4.2.8 betas.
And finally, to the second part of your reply. Since, according to what you wrote--if I haven't completely misunderstood that, which is entirely possible--your theory is that the coding error might originate from the current 4.2.8 version (that is, if "ntpd.c source file" is part of the 4.2.8). If so, should we all redo this entire thing when the one now in beta is in final release, as that might eliminate this error?
Sorry if all this has just added to the confusion, but I hope not.
Personally I'd be inclined to always use the latest release, beta or not. I don't know whether the bug will "go away" or not. It's apparently very rare.
