David L. Mills
mills at udel.edu
Mon Oct 11 09:03:29 PDT 2004
Well, it really and truly was working. I think the version now in
/backroom/ntp-sim is the one that works for me. I'm on campus now and
the ISDN line to the backroom is out again. I'll see what I can do later
Danny Mayer wrote:
> At 10:38 PM 10/10/2004, David L. Mills wrote:
>> Yes, I know the problem is with the client, but yes, the contraption
>> did really work up until recently. There was a little darling routine
>> in ntp_io.c I used to pry the address from the interface's cold dead
> Actually you don't have my new code so putting it back should not
> affect me.
> Are you sure it was really working? Which version was that? It would be
> worthwhile looking at to see what's changed so that it's no longer
> Also, the ntp key file permissions are wrong:
> 10 Oct 22:37:18 ntpd: can't open key file
> /usr/local/etc/ntp.keys: Permis
> sion denied
> However the permissions look okay since I'm running as root:
> -r-------- 1 root root 576 Dec 10 2000
> Maybe you understand better.
>> Yes, pogo is the only other public server here, but it is restricted
>> only for Autokey access. I suppose I could back out the ntp_io.c
>> routine and put back the old one from /backroom/ntp-sim, which was
>> known to work, but that of course would complicate your testing. If
>> this is something you think might work in a couple of days, I will
>> wait the distance.
> No, please don't wait. It's going to take longer than that. Right now,
> with wildcard
> turned off I don't see the broadcast packets at all. I'm running this
> right now as
> I right this on baldwin and it's not seeing any broadcast packets. I
> don't understand
> Why don't you pull in the older version for test purposes.
>> The problem with the ntpdc utility, at least, is that I and the USNO
>> and NIST keepers have a paper due in November and it uses data
>> gathered with monlist. However, that should be low on your priority
>> list if on the list at all.
> Unfortunately being a volunteer means I can't dedicate a lot of time
> to ntp. I'd
> like to look into this but my resources are limited and the I/O stuff
> is sucking
> up most of it.
More information about the hackers