Hello,
I am trying to configure some remote NTP servers in the XML config file to
be used with autoyast, and while it appears to be working, I would like to
know if I'm doing it the correct or best way.
Here is the <ntp> section from the config:
============================================================
<ntp-client>
false
<peers config:type="list">
<peer>
<address>127.127.1.0</address>
<comment>###################################################################
#############
## /etc/ntp.conf
##
## Sample NTP configuration file.
## See package 'ntp-doc' for documentation, Mini-HOWTO and FAQ.
## Copyright (c) 1998 S.u.S.E. GmbH Fuerth, Germany.
##
## Author: Michael Andres, <ma@suse.de>
##
############################################################################
####
##
## Radio and modem clocks by convention have addresses in the
## form 127.127.t.u, where t is the clock type and u is a unit
## number in the range 0-3.
##
## Most of these clocks require support in the form of a
## serial port or special bus peripheral. The particular
## device is normally specified by adding a soft link
## /dev/device-u to the particular hardware device involved,
## where u correspond to the unit number above.
##
## Generic DCF77 clock on serial port (Conrad DCF77)
## Address: 127.127.8.u
## Serial Port: /dev/refclock-u
##
## (create soft link /dev/refclock-0 to the particular ttyS?)
##
# server 127.127.8.0 mode 5 prefer
##
## Undisciplined Local Clock. This is a fake driver intended for backup
## and when no outside source of synchronized time is available.
##
</comment>
stratum 10 # LCL is
unsynchronized
false
<options> # local clock (LCL)</options>
<type>__clock</type>
</peer>
<peer>
<address>/var/lib/ntp/drift/ntp.drift # path for drift
file</address>
<comment>
##
## Outside source of synchronized time
##
## server xx.xx.xx.xx # IP address of server
##
## Miscellaneous stuff
##
</comment>
false
<options></options>
<type>driftfile</type>
</peer>
<peer>
<address>/var/log/ntp # alternate log
file</address>
<comment>
</comment>
false
<options></options>
<type>logfile</type>
</peer>
<peer>
<address>192.168.3.2</address>
<comment></comment>
true
<options></options>
<type>server</type>
</peer>
<peer>
<address>192.168.3.86</address>
<comment></comment>
false
<options></options>
<type>server</type>
</peer>
<peer>
<address>uk.pool.ntp.org</address>
<comment></comment>
false
<options></options>
<type>server</type>
</peer>
</peers>
true
true
</ntp-client>
============================================================
Our intention is to time sync from one (or both) of our internal servers
(192.168.3.x) or, if they are unavailable, sync from uk.pool.ntp.org.
Ideally, we would like to sync from 192.168.3.2 and 192.168.3.86 and to take
an average of the two, but I don't know if NTP works like this.
If it only syncs from a single server at a time, then 192.168.3.2 should be
attempted first, then 192.168.3.86, and then uk.pool.ntp.org.
Is our config going to give us what we require?
Thanks in advance to those who can help, it's very much appreciated :-)
Richard.
--
Richard Hobbs (Systems Administrator)
Toshiba Research Europe Ltd. - Speech Technology Group
Web: http://www.toshiba-europe.com/research/
Normal Email: richard.hobbs@crl.toshiba.co.uk
Mobile Email: mobile@mongeese.co.uk
Tel: +44 1223 376964 Mobile: +44 7811 803377
_____________________________________________________________________
This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
