Alexander S. Usov wrote:
On Tuesday 06 December 2005 11:30, [EMAIL PROTECTED] wrote:
Guillermo Ballester Valor wrote:
Hello,
I'm wondering it if is possible for SuSE/Nowell to install public NTP
time servers. These servers would be set as default in its xntp rpm
packages.
I'm mantaining a stratum-2 server in my home system with an ADSL
connection since three years ago. Many other volunteers are adding its
systems to pool.ntp.org
http://www.pool.ntp.org/
I think that to provide at least two or three stratum-1 servers (North
America, Europe, Australia ...) will be not dificult to Nowell.
At the installer, the user provides some localization information. From
that (most likely the timezone) a location can be derived which can be used
with the ntp-server to access (for me, in The Netherlands:
nl.pool.ntp.org).
How is this list maintained? The one's I use (ntp(0|1).nl.net) are not there.
They are not part of pool.ntp.org (at least not with that name). This
pool.ntp.org can be used as nl.pool.ntp.org (for The Netherlands) or
de.pool.ntp.org for germany and such. Then there are servers in broader ranges
like europe and such. This usage of <region>.pool.ntp.org can be relative
easy/automatic: the <region> is the tld of the same region. If that is not in
the dns, fall back to the larger region, ending in pool.ntp.org: nl.pool.ntp.org
-> eu.pool.ntp.org -> pool.ntp.org.
Then, only if ntp is installed and there is a direct connection to the
internet.
However: there are other ways to get a reasonable ntp-server: It can be
advertized in dhcp information, most current Windows Active Directory
servers do run some ntp protocol to which a workstation can do a reasonable
sync its clock.
And it even makes more sense than synchronizing to the "real" time, as in the
majority of the cases what really matter is a uniformity of the time in the
local network.
Nope, there are more time sync protocols, ntp is just one of them. Sntp is the
simplifyed version used in M$Windows active directory. Those can be used with
ntp and those can be advertised as ntp in the dhcp. Internally ntp uses epoch
time, which is a form of utc (gmt) as it is used in unix too. It is up to the
machine to translate this to local time: unix (and linux) does this only at the
moment the time is displayed to the user. Hence, the uniformity is part of the
protocol so it is taken care of.
CBee
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
