Bill Sommerfeld writes:
> What's in your ntp.conf file?
> 
> Looks like it's stuck attempting to register peers.  (a child process
> is forked to do the DNS resolves so they don't gum up NTP timings).

	server          ns1.cs.rmit.edu.au
	server          ns2.cs.rmit.edu.au
	driftfile       /var/db/ntp.drift

This is the same config file that my arm32, i386s, sparcs, and pmax
(all running -current (or close to)) have, and use successfully..


> Any interesting output in /var/log/messages?  Does ktrace show
> anything useful?

I restarted it, and this is what I get:

Nov 29 09:05:03 karybdis xntpd[22213]: 5.93c 3-NetBSD Wed Aug 12 10:05:25 EDT 1998 (1)
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 1 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 2 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 3 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 15 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 10 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 30 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 31 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 13 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: tickadj = 40, tick = 976, tvu_maxslew = 40920, est. hz = 1024
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 14 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: precision = 973 usec
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 23 had flags 2
Nov 29 09:05:03 karybdis xntpd[22213]: read drift of 0.000 from /var/db/ntp.drift
Nov 29 09:05:03 karybdis xntpd[22213]: signal_no_reset: signal 20 had flags 2


> > ntpq -c peers doesn't work either.
> 
> Define "doesn't work".  is it not responding, or is it showing no peers?

Doesn't respond:

	lukem@karybdis 7# ntpq -c peers
	localhost: timed out, nothing received
	***Request timed out


I'll try ktraceing the binary later today.