I coulda sworn I saw a lot of 'ntp dies' messages here last week,
but try as I might, I couldn't get Google to find them. So here goes.
It's a new install, everything rpm'ed- no tarballs or anything
complicated. The config file is below.
After a while, I get the '[processnumber] out of memory' message I
used to get in only 5-10 minutes; it now takes hours, so I must be
getting close. Rumor has it that only so much is malloc()ed, and when
enough statistics are gathered on available servers, it won't ask for
more, and ntp dies.
I mangled ntp every-which-way under FC2; this one breaks so easily
it's not even funny. Maybe it's something I'm doing wrong, can anyone
tell?
Thanks!
-----------------------------------------------------------------------
restrict default notrap nomodify nopeer
restrict 131.107.1.10 notrap nomodify
restrict 192.43.244.18 notrap nomodify
restrict 192.168.1.0 mask 255.255.255.0 notrap nomodify
server 127.127.1.0 # local clock (LCL)
fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
driftfile /etc/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
server time-nw.nist.gov prefer
server time.nist.gov
-----------------------------------------------------------------------
--
------------------------------------------------------------------------
Brian FahrlÃnder Christian, Conservative, and Technomad
Evansville, IN http://www.fahrlander.net
ICQ 5119262
AIM: WheelDweller
------------------------------------------------------------------------
Attachment:
signature.asc
Description: This is a digitally signed message part
