[EMAIL PROTECTED] wrote: > I know ntp is running because it updates the driftfile, > and ps shows it's active: > > # ps -aux | grep ntp > root 81 0.0 0.2 1328 960 ?? Ss 9Jan04 1:06.65 > /usr/sbin/ntpd -p /var/run/ntpd.pid > root 83 0.0 0.2 1364 992 ?? S 9Jan04 0:15.67 > /usr/sbin/ntpd -p /var/run/ntpd.pid > root 47532 0.0 0.0 304 164 p0 R+ 2:14AM 0:00.00 grep > ntp
I'm not sure why you have 2 ntpd processes running there - I only ever see one: (505) llama:~ $ ps uaxww | grep ntpd root 77934 0.0 0.2 1312 900 ?? Ss Sun04pm 0:12.45 /usr/sbin/ntpd -p /var/run/ntpd.pid I'd suggest killing both of those ntpd processes and starting it up again. Actually, before you restarting, try manually synchronising with one of your servers, eg: # ntpdate subitaneous.cpsc.ucalgary.ca That will at least tell you that you can talk NTP with this server. I assume all the servers in your ntp.conf are public ones that your host is allowed to use? The firewall rules look OK, although you might want to add 'log' to your default block rule while diagnosing a problem like this, so you'll be told if ipf is blocking any of the packets you're interested in. Scott _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"