NTPD unable to adjust local clock

Matthew Dillon dillon at apollo.backplane.com
Wed Apr 6 11:57:30 PDT 2005

:>>     we'd have to import the code for real and maintain it in our tree.
:> No xntpd please.
:What reason? I hope, 'BSD vs GPL' isn't one of main reason. All I care are
:function; not license. It works better than OpenNTPD.
:> I'm much more willing to write the actual slew algorithm for OpenNTPD,
:> which already has all the network code, only the actual adjust has to be
:> improved. I'm also quite sure that Henning would include it in OpenNTPD.
:You should keep old and not replace to OpenNTPD yet. I personal think you
:should put old back in and move OpenNTPD to ports. When OpenNTPD is ready
:and better than old, then you can replace it. Maybe too late for that but
:need improvement on one of your practice in future.
:> Joerg

    xntpd is very complex and potentially more of a security risk because
    of that complexity.

    If I had caught this earlier I would have reverted to xntpd... but it's
    too close to the release now so we are going to have to stick with
    OpenBSD's ntpd and Joerg can fix it post-release (or we can switch back
    to xntpd if we do not have anything working in the current ntpd 
    3 months from now).

    I had just assumed that they were using ntp_adjtime() and didn't check
    when the original code was imported.  My bad.

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Users mailing list