I've built a dual-core AMD64 system, but I cannot get ntpd to work. I'm
using debian unstable, 2.6.24-1-amd64, which is apparently really x86_64.
"ntpdate sever_name" will reset the system clock. ntp, when started,
will also set the system clock if needed.
ntpd then never synchronizes to another ntp as a peer, which means there
are no further adjustments to the time. The system clock falls behind
very quickly, on the order of minutes per hour.
This is not a firewall problem: all the other Linux, XP and MacOS boxes
synchronize without any problems. Please note that I have removed all
'restrict' statements from /etc/ntp.conf -- and I can't even sync to a
local server that easily syncs over the 'net.
I've tried a few (well, perhaps all) the recipes I could find on the
web; for example, booting with "no_timer_check" and/or "noapic."
Unfortunately, if there's a documentation repository that explains these
flags I have yet to find it -- and this does not fix the problem.
QUESTION: Other than running ntpdate as a cron job every five minutes,
is there some way to get ntpd to work correctly? For example, is there a
kernel module that needs to be rebuilt with different flags?
--
Moshe Yudkowsky * [EMAIL PROTECTED] * www.pobox.com/~moshe
"From stupidity there is always something to be learned, but
it's always the same thing: don't be stupid." -- Robert M. Adams
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
