On 5/8/2011 5:07 AM, Spyros Tsiolis wrote:
OK,
So what you people say is :
1. Run "ntpdate" during startup only once
2. After that, keep time with ntpd
Right ?
Yes, or run ntpd with the -g option. You don't want to use
the -x option (as some might have suggested) as that can cause
ntpd to take up to 2 weeks to synchronize the time.
Detailed ntp setup is OT for this list, but make sure your
ntp.conf lists at least three servers. Typically the ntp.org
pool servers will work fine, eg.
server 0.uk.pool.ntp.org
server 1.uk.pool.ntp.org
server 2.uk.pool.ntp.org
server 3.uk.pool.ntp.org
Then once in a while make sure ntp is running and
syncronised. I like "ntpq -p" which will show the peerlist
with a "*" next to the current master. ntpd works best on a
long-running server, and typically shouldn't be used on a
virtual server. Virtual environments have their own time service.
-- Noel Jones
