On Mar 26, 2009, at 8:44 AM, Chris Davies wrote:
leo <leona...@softel.cu> wrote:
when I exec ntpdate -u pool.ntp.org for example, the out is:
"no server suitable for synchronization found"
The NTP Pool servers are all run on a "best endeavours" basis. (I
know,
because I run one.) So if one doesn't respond you should try the next.
Since you're running debian, the "correct" pool servers to try are
these:
0.debian.pool.ntp.org
1.debian.pool.ntp.org
2.debian.pool.ntp.org
3.debian.pool.ntp.org
Ideally, instead of using ntpdate you should seriously consider
running
the ntp daemon itself (ntpd) from package 'ntp'. This has these
servers
preconfigured, and it also steps the time correctly at boot so there's
almost no need for ntpdate.
Chris
Chris is absolutely right. The ntpdate program is no longer necessary
with modern ntp daemons. The ntpd daemon knows enough to step the
clock one time if it needs it at startup time.
Personally, I like to change the "server #.debian.pool.ntp.org" lines
to "server #.us.pool.ntp.org" to make sure that the servers I'm using
are geography-wise and network-topology-wise close by. Now, of
course, if you don't live in the US, you should use your own country-
code instead. But, of course again, if your country is so small that
it doesn't have enough ntp servers to be useful, try picking one or
more nearby countries with a larger flock of ntp servers.
But then, I'm a time fanatic. For most normal people, the debian pool
servers in the unmodified /etc/ntp.conf file will do just fine.
Enjoy!
Rick
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
