Problem
SCO Servers have timekeeping limitations that I need to resolve.
Cause
A. The stability of personal computer clock chips varies from
manufacturer to manufacturer, resulting in some being more
efficient than others.B. The time of day (TOD) clock is kept by a kernel driver. This
driver must compete with other devices drivers for interrupts
and processor time. If a driver running at a high priority
prevents a clock interrupt from being responded to immediately,
it will be "queued up". However, there is no mechanism in the
hardware to record how many of some interrupts have occurred
before it is responded to. Thus, if the driver operates at a
high priority for long enough that two or more clock interrupts
have occurred, when the clock driver finally runs, only one
clock tick will be counted, resulting in lost clock ticks. Solution
To alter the timekeeping limitations in the kernel, configure and run xntpd(ADMN) in client mode.
For OpenServer 5.0.0, 5.0.2, and 5.0.4, TLS618 is required in order
for xtnpd to work properly. This TLS may be downloaded from the SCO
ftp site.Roughly similar to the hierarchical structure that DNS provides for machine name to IP address resolution, xntpd(ADMN) servers provide a hierarchical structure for handling time queries.
A top level xntpd server is referred to as "stratum 0" server. As
the level of remoteness from the level zero server increases, the
stratum level number increases (stratum 1, stratum 2, and so on).Ideally, a stratum 0 server is connected to an extremely accurate
timekeeping device, such as an atomic clock. In practice, many
stratum 0 servers are self-contained and rely on their own internal
hardware clocks.There are several basic modes of operation for which xntpd can be configured:
* client - only queries the timeserver and updates itself with the time it receives.
* peer - behaves as a lower level timeserver, servicing client
time queries. It will also will query servers with a lower
and equal stratum level to itself and will update its own time
based on the results of such queries.* advertising server - like a peer, but will broadcast time values for clients on the local net.
* stratum 0 - will query only itself for the time and will only receive an update from itself. Will service time queries from clients and servers with a higher stratum number than themselves.
In choosing an xntpd server, look for a machine in the same time zone and with the fewest number of network hops in distance. You can use traceroute(ADMN) to find out how many hops away the server machine is, if it is not on your local network.
By default, /etc/ntp.conf file does not exist, and must be created
by the system administrator. This is the primary configuration file
for xntpd. If this file exists, then the xntpd binary will be
started when the system goes into multiuser mode. Depending on the
contents of the file, it will be configured as a client, peer, or
server.An example of an /etc/ntp.conf client configuration follows:
#
# sample /etc/ntp.conf file CLIENT configuration
#
#
server 132.147.210.9# ^ The IP address of the stratum 0 server machine that you would
# be asking for the time.peer 132.147.144.30# ^ The IP address of a higher stratum level server machine of
# which you would ask the time.peer 132.147.144.13
resolver /etc/xntpres# ^ Mandatory entry to specify IP/name resolution used by xntpd
# since it does not use DNSdriftfile /etc/driftfile# ^ A scratch file used by xntpd for time adjustmentNOTE: If you want to refer to a stratum 0 level timeserver that is
connected to an atomic clock and is publically accessible via the
Internet, point your WWW browser to the following URL:http://www.eecis.udel.edu/~mills/ntp/clock1.htmlFurther, many Internet Service Providers (ISPs) have NTP servers available for their clients to access. Ask your ISP for availability.