Dave, I've fixed that to be public. In this case it was a Windows bug and was not so much an NTP problem as a Windows problem when receiving and sending NTP packets. I fixed the bug a couple of days ago.
You can get to it now, though I don't think you should have any cause for concern about its affect on NTP. Danny David L. Mills wrote: > Steve, > > I just tried it for the third time and it broke again. However, under > the blinding red banner is very a hard to read statement (I had to use a > magnifying glass) that I must log in to read the report, which explains > my problem. I don't log into anywhere with name and password unless > requested by an official employer or govenment organization. > Accordingly, I'm not going to see the report. If somebody thinks I > should see it, send it to me in the clear, as in fact often happens when > I am requested to respond to bug reports. > > Dave > > Steve Kostecke wrote: > >> On 2007-05-25, David L. Mills <[EMAIL PROTECTED]> wrote: >> >> >>> Oops. The link that broke is/was http://bugs.ntp.isc.org/527 >> >> I just tried that link (again) and it works for me. That URL should lead >> you to https://ntp.isc.org/bugs/show_bug.cgi?id=527. >> >> I also grepped the logs for that virtual server and did not find any 404 >> errors for that URL. >> > > _______________________________________________ > questions mailing list > [email protected] > https://lists.ntp.isc.org/mailman/listinfo/questions > _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
