On Wed, 2009-04-08 at 09:33 -0500, Charles Jennings wrote:
Doesn't look like it - here is some more info:
Chkconfig --list
ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
/etc/crontab
01 * * * * root /usr/sbin/ntpd -q > /dev/null &
/etc/sysconfig/ntpd
# Drop root to id 'ntp:ntp' by default. OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid"
# Set to 'yes' to sync hw clock after successful ntpdate SYNC_HWCLOCK=yes
# Additional options for ntpdate NTPDATE_OPTIONS=""
/etc/ntp.conf
restrict default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery
restrict 127.0.0.1 restrict -6 ::1
server time.nist.gov iburst server 127.127.1.0 fudge 127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
keys /etc/ntp/keys
Hmm.. you could try to strace the ntpd process to see how it tries to send log messages. It might use its own syslog() implementation instead of relying on libc and thus fail because of a mismatching UNIX domain socket type. (dgram vs. stream) -- Bazsi