aboutsummaryrefslogtreecommitdiff
path: root/html/build
diff options
context:
space:
mode:
Diffstat (limited to 'html/build')
-rw-r--r--html/build/build.html83
-rw-r--r--html/build/config.html168
-rw-r--r--html/build/hints.html23
-rw-r--r--html/build/hints/a-ux195
-rw-r--r--html/build/hints/aix76
-rw-r--r--html/build/hints/bsdi65
-rw-r--r--html/build/hints/changes13
-rw-r--r--html/build/hints/decosf140
-rw-r--r--html/build/hints/decosf254
-rw-r--r--html/build/hints/freebsd15
-rw-r--r--html/build/hints/hpux158
-rw-r--r--html/build/hints/linux5
-rw-r--r--html/build/hints/mpeix50
-rw-r--r--html/build/hints/netbsd37
-rw-r--r--html/build/hints/notes-xntp-v3119
-rw-r--r--html/build/hints/parse105
-rw-r--r--html/build/hints/refclocks35
-rw-r--r--html/build/hints/rs600056
-rw-r--r--html/build/hints/sco.html24
-rw-r--r--html/build/hints/sgi74
-rw-r--r--html/build/hints/solaris-dosynctodr.html321
-rw-r--r--html/build/hints/solaris.html144
-rw-r--r--html/build/hints/solaris.xtra.402311836
-rw-r--r--html/build/hints/solaris.xtra.409584974
-rw-r--r--html/build/hints/solaris.xtra.S99ntpd21
-rw-r--r--html/build/hints/solaris.xtra.patchfreq85
-rw-r--r--html/build/hints/sun415
-rw-r--r--html/build/hints/svr4-dell8
-rw-r--r--html/build/hints/svr4_package33
-rw-r--r--html/build/hints/todo4
-rw-r--r--html/build/hints/vxworks.html82
-rw-r--r--html/build/hints/winnt.html281
-rw-r--r--html/build/patches.html36
-rw-r--r--html/build/porting.html40
-rw-r--r--html/build/quick.html30
-rw-r--r--html/build/scripts/footer.txt7
-rw-r--r--html/build/scripts/links10.txt5
-rw-r--r--html/build/scripts/links11.txt5
-rw-r--r--html/build/scripts/links12.txt5
-rw-r--r--html/build/scripts/links7.txt5
-rw-r--r--html/build/scripts/links8.txt6
-rw-r--r--html/build/scripts/links9.txt7
-rw-r--r--html/build/scripts/style.css64
43 files changed, 0 insertions, 2709 deletions
diff --git a/html/build/build.html b/html/build/build.html
deleted file mode 100644
index 0bb49afda319..000000000000
--- a/html/build/build.html
+++ /dev/null
@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <meta name="generator" content="HTML Tidy, see www.w3.org">
- <title>Building and Installing the Distribution</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h3>Building and Installing the Distribution</h3>
- <img src="../pic/beaver.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/%7emills/pictures.html">from <i>Pogo</i>, Walt Kelly</a>
- <p>For putting out compiler fires.</p>
- <p>Last update: <csobj format="ShortTime" h="25" locale="00000409" region="0" t="DateTime" w="99">03:06 AM</csobj> UTC <csobj format="LongDate" h="25" locale="00000409" region="0" t="DateTime" w="270">Monday, October 13, 2003</csobj></p>
- <br clear="left">
- <h4>Related Links</h4>
- <script type="text/javascript" language="javascript" src="scripts/links7.txt"></script>
- <h4>Table of Contents</h4>
- <ul>
- <li class="inline"><a href="#build">Building and Installing the Distribution</a>
- <li class="inline"><a href="#unix">Building and Installing under Unix</a>
- <li class="inline"><a href="#comp">Compilation</a>
- <li class="inline"><a href="#install">Installation</a>
- <li class="inline"><a href="#config">Configuration</a>
- <li class="inline"><a href="#prob">If You Have Problems</a>
- <li class="inline"><a href="#win">Building and Installing under Windows NT</a>
- </ul>
- <hr>
- <h4 id="build">Building and Installing the Distribution</h4>
- <p>As a practical matter, every computer architecture and operating system version seems to be different than any other. The device drivers may be different, the input/output system may be idiosyncratic and the libraries may have different semantics. It is not possible in a software distribution such as this one to support every individual system with a common set of binaries, even with the same system but different versions. Therefore, it is necessary to individually configure the software build for each system and version, both at compile time and at run time. In almost all cases, these procedures are completely automatic and all the newbie user need do is type &quot;configure&quot;, &quot;make&quot; and &quot;install&quot; in that order and the autoconfigure system does the rest. There are some exceptions, as noted below and on the <a href="hints.html">Hints and Kinks</a> page.</p>
- <p>If available, the OpenSSL library from <a href="http://www.openssl.org">http://www.openssl.org</a> is used to support public key cryptography. The library must be built and installed prior to building NTPv4. The procedures for doing that are included in the OpenSSL documentation. The library is found during the normal NTPv4 configure phase and the interface routines compiled automatically. Only the <tt>libcrypto.a</tt> library and associated header files are used. If the library is not available or disabled, this step is not required.</p>
- <h4 id="unix">Building and Installing under Unix</h4>
- <p>Make sure that you have all necessary tools for building executables. These tools include <tt>cc/gcc, make, awk, sed, tr, sh, grep, egrep</tt> and a few others. Not all of these tools exist in the standard distribution of modern Unix versions (compilers are likely to be an add-on product). If this is the case, consider using the GNU tools and <tt>gcc</tt> compiler. For a successful build, all of these tools should be accessible via the current path.</p>
- <p>The first thing to do is uncompress the distribution and extract the source tree. In the distribution base directory use the <tt>./configure</tt> command to perform an automatic configuration procedure. This command inspects the hardware and software environment and tests for the presence of system header files and the contents of these files to determine if certain features are present. When one or more of these features are present, the code is compiled to use them; if not, no special code is compiled. However, even if the code is compiled to use these features, the code does a special test at run time to see if one or more are actually present and avoids using them if not present. In such cases a warning message is sent to the system log, but the daemon should still work properly.</p>
- <p>The default build normally includes the debugging code, which can be useful in diagnosing problems found in initial test, and all reference clock drivers known to work with each machine and operating system. Unless memory space is at a premium, this is a sensible strategy and greatly simplifies debugging and support. If you need to delete either the debugging code or one or all reference clock drivers to save space, see the <a href="config.html">Configuration Options</a> page.</p>
- <p>If your site supports multiple architectures and uses NFS to share files, you can use a single source tree to compile executables for all architectures. While running on a target architecture machine and in the distribution base directory create a subdirectory using a command like <tt>mkdir A.`config.guess`</tt>, which will create an architecture-specific directory with name peculiar to the architecture and operating system. Then change to this directory and emit a <tt>../configure</tt> command. The remaining steps are the same whether building in the base directory or in the subdirectory.</p>
- <h4 id="comp">Compilation</h4>
- <p>Use the <tt>make</tt> command to compile all source modules, construct the libraries and link the distribution. Expect few or no warnings using <tt>cc</tt> and a moderate level of warnings using <tt>gcc</tt>. Note: On some Unix platforms <tt>gcc</tt> may show quite a few complaints about system header files and type inconsistencies, especially with pointer variables. This is usually the case when the system header files are not up to ANSI standards or <tt>gcc </tt>expectations, when <tt>gcc</tt> is not installed properly, or when operating system updates and patches are applied and <tt>gcc</tt> is not reinstalled. While the autoconfigure process is quite thorough, the Unix programming cultures of the various workstation makers still remain idiosyncratic.</p>
- <h4 id="install">Installation</h4>
- <p>As root, use the <tt>make install</tt> command to install the binaries in the destination directory. Most commonly, these programs are installed in <tt>/usr/local/bin</tt>, but this can be overridden during configuration. You must of course have write permission on the install in the destination directory. This includes the following programs:</p>
- <ul>
- <li><a href="../ntpd.html"><tt>ntpd</tt> - Network Time Protocol (NTP) daemon</a>
- <li><a href="../ntpq.html"><tt>ntpq</tt> - standard NTP query program</a>
- <li><a href="../ntpdc.html"><tt>ntpdc</tt> - special NTP query program</a>
- <li><a href="../ntpdate.html"><tt>ntpdate</tt> - set the date and time via NTP</a>
- <li><a href="../ntptrace.html"><tt>ntptrace</tt> - trace a chain of NTP servers back to the primary source</a>
- </ul>
- <p>If the precision time kernel modifications are present, the following program is installed:</p>
- <ul>
- <li><a href="../ntptime.html"><tt>ntptime</tt> - read kernel time variables</a>
- </ul>
- <p>If the public key authentication functions are present, the following program is installed:</p>
- <ul>
- <li><a href="../keygen.html"><tt>ntp-keygen</tt> - generate public and private keys</a>
- </ul>
- <p>In some systems that include the capability to edit kernel variables, the following program is installed:</p>
- <ul>
- <li><a href="../tickadj.html"><tt>tickadj</tt> - set time-related kernel variables</a>
- </ul>
- <p>Cryptographic support, both symmetric and public key, requires one or more key files, commonly installed in <tt>/usr/local/etc</tt>. Public key cryptography requires a random seed file, usually called <tt>.rnd</tt>, installed in a dark place such as the root directory or <tt>/etc</tt>. Directions for generating keys is on the <a href="../authopt.html">Authentication Options</a> page.</p>
- <h4 id="config">Configuration</h4>
- <p>You are now ready to configure the daemon and start it. You will need to create a NTP configuration file <tt>ntp.conf</tt> and a cryptographic key file <tt>ntp.keys</tt>. The latter file is necessary only for remote configuration support, if needed. Newbies should see the <a href="quick.html">Quick Start</a> page for orientation. Seasoned veterans can start with the <a href="../ntpd.html"><tt>ntpd</tt> - Network Time Protocol (NTP) daemon</a> page and move on to the specific configuration option pages from there. A tutorial on NTP subnet design and configuration options is in the <a href="../notes.html">Notes on Configuring NTP and Setting up a NTP Subnet</a> page.</p>
- <h4 id="prob">If You Have Problems</h4>
- <p>If you have problems peculiar to the particular hardware and software environment (e.g. operating system-specific issues), browse the <a href="hints.html">Hints and Kinks</a> page. For other problems a tutorial on debugging technique is in the <a href="../debug.html">NTP Debugging Technique</a> page. As always, the first line of general assistance is the NTP web site <a href="http://www.ntp.org">www.ntp.org</a> and the FAQ resident there. Requests for assistance of a general nature and of interest to other timekeepers should be sent to the NTP newsgroup comp.protocols.time.ntp. Bug reports of a specific nature should be sent to <a href="mailto:bugs@mail.ntp.org">bugs@ntp.org</a>. Bug reports of a specific nature on features implemented by the programmer corps mentioned in the <a href="../copyright.html">Copyright</a> page should be sent directly to the implementor listed in that page, with copy to bugs@ntp.org.</p>
- <p>Please include the version of the source distribution (e.g., ntp-4.0.70a) in your bug report, as well as billboards from the relevant utility programs and debug trace, if available. Please include the output of <tt>config.guess</tt> in your bug report. It will look something like:</p>
- <p><tt>pdp11-dec-fuzzos3.4</tt></p>
- <h4>Additional <tt>make</tt> commands</h4>
- <dl>
- <dt><tt>make clean</tt>
- <dd>Cleans out object files, programs and temporary files.
- <dt><tt>make distclean</tt>
- <dd>Does the work of <tt>clean</tt>, but cleans out all directories in preparation for a new distribution release.
- <dt><tt>make dist</tt>
- <dd>Does the work of <tt>make distclean</tt>, but constructs compressed tar files for distribution. You must have GNU automake to perform this function.
- </dl>
- <h4 id="win">Building and Installing under Windows NT</h4>
- <p>See <tt><a href="hints/winnt.html">hints/winnt.htm</a></tt> for directions to compile the sources and install the executables.</p>
- <hr>
- <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
- </body>
-
-</html> \ No newline at end of file
diff --git a/html/build/config.html b/html/build/config.html
deleted file mode 100644
index 961779de66e7..000000000000
--- a/html/build/config.html
+++ /dev/null
@@ -1,168 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <meta name="generator" content="HTML Tidy, see www.w3.org">
- <title>Configuration Options</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h3>Configuration Options</h3>
- <img src="../pic/pogo3a.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/%7emills/pictures.html">from <i>Pogo</i>, Walt Kelly</a>
- <p>Gnu autoconfigure tools are in the backpack.</p>
- <p>Last update: <csobj format="ShortTime" h="25" locale="00000409" region="0" t="DateTime" w="99">12:56 AM</csobj> UTC <csobj format="LongDate" h="25" locale="00000409" region="0" t="DateTime" w="266">Saturday, March 20, 2004</csobj></p>
- <br clear="left">
- <h4>Table of Contents</h4>
- <ul>
- <li class="inline"><a href="#basic">Basic Configuration Options - the <tt>configure</tt> utility</a>
- <li class="inline"><a href="#opt">Options</a>
- <li class="inline"><a href="#dir">Directory and File Names</a>
- <li class="inline"><a href="#host">Host Type</a>
- <li class="inline"><a href="#pkg">Optional Packages</a>
- <li class="inline"><a href="#feat">Optional Features</a>
- <li class="inline"><a href="#radio">Radio Clocks</a>
- <li class="inline"><a href="#parse">PARSE Clocks</a>
- </ul>
- <hr>
- <h4 id="basic">Basic Configuration Options - the <tt>configure</tt> utility</h4>
- <p>The following options are for compiling and installing a working version of the NTP distribution. In most cases, the build process is completely automatic. In some cases where memory space is at a premium, or the binaries are to be installed in a different place, it is possible to tailor the configuration to remove such features as reference clock driver support, debugging support, and so forth.</p>
- <p>Configuration options are specified as arguments to the <tt>configure</tt> script. Following is a summary of the current options, as of the 4.0.99m version:</p>
- <p>Usage: <tt>configure [options] [host]</tt><br>
- </p>
- <h4 id="opt">Options</h4>
- <p><tt>[defaults in brackets after descriptions]</tt> Configuration:</p>
- <pre>
- --cache-file=FILE cache test results in FILE
- --help print this message
- --no-create do not create output files
- --quiet, --silent do not print `checking...' messages
- --version print the version of autoconf that created
-configure
-</pre>
- <h4 id="dir">Directory and File Names</h4>
- <pre>
- --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local]
- --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [same as prefix]
- --bindir=DIR user executables in DIR [EPREFIX/bin]
- --sbindir=DIR system admin executables in DIR [EPREFIX/sbin]
- --libexecdir=DIR program executables in DIR [EPREFIX/libexec]
- --datadir=DIR read-only architecture-independent data in DIR [PREFIX/share]
- --sysconfdir=DIR read-only single-machine data in DIR [PREFIX/etc]
- --sharedstatedir=DIR modifiable architecture-independent data in DIR [PREFIX/com]
- --localstatedir=DIR modifiable single-machine data in DIR [PREFIX/var]
- --libdir=DIR object code libraries in DIR [EPREFIX/lib]
- --includedir=DIR C header files in DIR [PREFIX/include]
- --oldincludedir=DIR C header files for non-gcc in DIR [/usr/include]
- --infodir=DIR info documentation in DIR [PREFIX/info]
- --mandir=DIR man documentation in DIR [PREFIX/man]
- --srcdir=DIR find the sources in DIR [configure dir or ..]
- --x-includes=DIR X include files are in DIR
- --x-libraries=DIR X library files are in DIR
- --program-prefix=PREFIX prepend PREFIX to installed program names
- --program-suffix=SUFFIX append SUFFIX to installed program names
- --program-transform-name=PROGRAM run sed PROGRAM on installed program names
-</pre>
- <h4 id="host">Host Type</h4>
- <pre>
- --build=BUILD configure for building on BUILD [BUILD=HOST]
- --host=HOST configure for HOST [guessed]
- --target=TARGET configure for TARGET [TARGET=HOST]
-</pre>
- <h4 id="pkg">Optional Packages</h4>
- <pre>
- --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
- --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
-
- openssl-libdir=DIR OpenSSL object code libraries in DIR [/usr/lib/usr/local/lib/usr/local/ssl/lib]
- openssl-incdir=DIR OpenSSL header files in DIR [/usr/include/usr/local/include/usr/local/ssl/include]
- crypto=autokey Use autokey cryptography
- crypto=rsaref Use the RSAREF library
- electricfence Compile with ElectricFence malloc debugger
-</pre>
- <h4 id="feat">Optional Features</h4>
- <pre>
- --disable-FEATURE do not include FEATURE (same as
- --enable-FEATURE=no)
- --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
-
- accurate-adjtime The adjtime() call is accurate
- clockctl use /dev/clockctl (non root control of system clock)
- debugging Include debugging code [enable]
- des Include support for DES keys [enable]
- dst-minutes=VALUE Minutes per DST adjustment [60]
- gdt-surveying Include GDT survey code [disable]
- hourly-todr-sync If we should sync TODR hourly
- kernel-fll-bug If we should avoid a (Solaris) kernel FLL bug
- kmem Read /dev/kmem for 'tick' and/or 'tickadj'
- md5 Include support for MD5 keys [enable]
- ntpdate-step If ntpdate should step the time
- slew-always Always slew the time
- step-slew Step and slew the time
- tick=VALUE Force a value for 'tick'
- tickadj=VALUE Force a value for 'tickadj'
- udp-wildcard Use UDP wildcard delivery
-</pre>
- <h4 id="radio">Radio Clocks</h4>
- <p>(these are ordinarily enabled, if supported by the machine and operating system):</p>
- <pre>
- all-clocks Include drivers for all suitable non-PARSE clocks [enable]
- ACTS NIST dialup clock
- ARBITER Arbiter 1088A/B GPS receiver
- ARCRON_MSF Arcron MSF receiver
- AS2201 Austron 2200A or 2201A GPS receiver
- ATOM ATOM PPS interface
- AUDIO-CHU CHU audio decoder
- BANCOMM Datum/Bancomm BC635/VME interface (requires an explicit --enable-BANCOMM request)
- CHRONOLOG Chrono-log K-series WWVB receiver
- CHU CHU modem decoder
- DATUM Datum Programmable Time System
- DUMBCLOCK Dumb generic hh:mm:ss local clock
- FG Forum Graphic GPS
- GPSVME TrueTime GPS receiver with VME interface (requires an explicit --enable-GPSVME request)
- HEATH HeathKit GC-1000 Most Accurate Clock
- HOPFPCI HOPF 6039 PCI board
- HOPFSERIAL HOPF serial clock device
- HPGPS HP 58503A GPS Time &amp; Frequency receiver
- IRIG IRIG (Audio) Clock
- JUPITER Rockwell Jupiter GPS receiver
- LEITCH Leitch CSD 5300 Master Clock System Driver
- LOCAL-CLOCK Local clock driver
- MSFEES EES M201 MSF receiver
- MX4200 Magnavox MX4200 GPS receiver
- NMEA NMEA GPS receiver
- ONCORE Motorola VP/UT Oncore GPS receiver
- PALISADE Palisade clock
- PCF Conrad parallel port radio clock
- PST PST/Traconex 1020 WWV/H receiver
- PTBACTS PTB dialup clock support
- SHM Clock attached through shared memory (requires an explicit --enable-SHM request)
- SPECTRACOM Spectracom 8170/Netclock/2 WWVB receiver
- TRAK TRAK 8810 GPS station clock
- TPRO KSI/Odetics TPRO/S IRIG Interface
- TRUETIME Kinemetrics/TrueTime (generic) receiver
- ULINK Ultralink WWVB receiver
- USNO US Naval Observatory dialup clock
- WWV WWV audio receiver
-</pre>
- <h4 id="parse">PARSE Clocks</h4>
- <pre>
- parse-clocks Include drivers for all suitable PARSE clocks [enable]
- COMPUTIME Diem Computime Radio Clock
- DCF7000 ELV/DCF7000 Clock
- HOPF6021 HOPF 6021 Radio Clock support
- MEINBERG Meinberg clocks
- RAWDCF DCF77 raw time code
- RCC8000 RCC 8000 Radio Clock support
- SCHMID SCHMID DCF77 clock support
- TRIMTAIP Trimble GPS/TAIP Protocol
- TRIMTSIP Trimble GPS/TSIP Protocol
- VARITEXT VARITEXT clock
- WHARTON Wharton 400A Series clock
-</pre>
- <hr>
- <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
- </body>
-
-</html> \ No newline at end of file
diff --git a/html/build/hints.html b/html/build/hints.html
deleted file mode 100644
index b9e230ba234e..000000000000
--- a/html/build/hints.html
+++ /dev/null
@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <title>Hints and Kinks</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h3>Hints and Kinks</h3>
- <img src="../pic/alice35.gif" align="left" alt="gif"><a href="http://www.eecis.udel.edu/%7emills/pictures.html"> from <i>Alice's Adventures in Wonderland</i>, Lewis Carroll</a>
- <p>Mother in law has all the answers.</p>
- <p>Last update: <csobj format="ShortTime" h="25" locale="00000409" region="0" t="DateTime" w="99">12:56 AM</csobj> UTC <csobj format="LongDate" h="25" locale="00000409" region="0" t="DateTime" w="266">Saturday, March 20, 2004</csobj></p>
- <br clear="left">
- <hr>
- <p>This is an index for a set of troubleshooting notes contained in individual text files in the <tt>./hints</tt> directory. They were supplied by various volunteers in the form of mail messages, patches or just plain word of mouth. Each note applies to a specific computer and operating system and gives information found useful in setting up the NTP distribution or site configuration. The notes are very informal and subject to errors; no attempt has been made to verify the accuracy of the information contained in them.</p>
- <p>Additions or corrections to this list or the information contained in the notes is solicited. The most useful submissions include the name of the computer manufacturer (and model numbers where appropriate), operating system (specific version(s) where appropriate), problem description, problem solution and submitter's name and electric address. If the submitter is willing to continue debate on the problem, please so advise. See the <a href="hints/">directory listing</a>.</p>
- <hr>
- <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
- </body>
-
-</html> \ No newline at end of file
diff --git a/html/build/hints/a-ux b/html/build/hints/a-ux
deleted file mode 100644
index f8c26d2188b6..000000000000
--- a/html/build/hints/a-ux
+++ /dev/null
@@ -1,195 +0,0 @@
--------------
-INTRODUCTION:
--------------
-Last revision: 06-Jul-1994
-
-Included in this distribution of XNTP V3 is a configuration file suitable
-for use under Apple's A/UX Version 3.x.x There is also one for A/UX 2.0.1
-but it has not been fully tested. To make the executables follow the steps
-outlined below.
-
-*** NOTE: You must have gcc installed to successfully compile the current
-distribution; the native cc supplied with A/UX will NOT correctly compile
-this source. See the FAQ in comp.unix.aux for places to obtain gcc from
-and how to install it.
-
-----------------------
-MAKING XNTPD FOR A/UX:
-----------------------
-
-First, you need to create the makefiles (after you've downloaded the
-source, of course):
-
- % make clean
- % make refconf
-
-After that, you should edit Config.local to make sure that BINDIR is
-correct for where you wish the programs to be "installed". The default
-(and what I use) is /usr/local/etc. Make sure that DEFS_LOCAL and
-CLOCKDEFS are commented out! Presently, only the LOCAL_CLOCK/REFCLOCK
-clock is used and supported.
-
-
-After this is done (you should be told that your system is A/UX 3), make
-'xntpd' (the options to 'gcc' are held in compilers/aux3.gcc):
-
- % make
-
-I do not normally use the `make install' option and so have not verified its
-compatibility with A/UX. Rather, I pull out each of the executables and
-place them in the locally appropriate locations.
-
----------------
-STARTING XNTPD:
----------------
-
-At this point you need to set things up so that 'xntpd' is started upon
-boot-up. You can do this in 1 of 2 ways: either add entries in /etc/inittab
-or, more ideally, create and use an /etc/rc.local file. Since rc.local is
-what I recommend, here's how you do it:
-
-By default, A/UX doesn't have rc.local, so you'll need to add the following to
-/etc/inittab:
-
- net6:2:wait:/etc/syslogd # set to "wait" to run a syslog daemon
-+ jmj0:2:wait:/etc/rc.local 1>/dev/syscon 2>&1 # Local stuff
- dbg2::wait:/etc/telinit v # turn off init's verbose mode
-
-Now, the look of a sample /etc/rc.local is as follows:
-
- #!/bin/sh
- :
- : rc.local
- :
- # @(#)Copyright Apple Computer 1987 Version 1.17 of rc.sh on 91/11/08 15:56:21 (ATT 1.12)
-
-
- # Push line discipline/set the device so it will print
- /etc/line_sane 1
- echo " "
- echo "Entering rc.local..."
-
- set `/bin/who -r`
- if [ "$7" = 2 ]
- then
- /bin/echo " now setting the time..."
- /usr/local/etc/ntpdate -s -b <host.domain>
- sleep 5
- #
- # start up 'xntpd' if we want
- #
- if [ -f /etc/ntp.conf ]
- then
- /bin/echo " setting tick and tickadj..."
- /usr/local/etc/tickadj -t 16672 -a 54
- sleep 5
- /bin/echo " starting xntpd..."
- /usr/local/etc/xntpd <&- > /dev/null 2>&1
- sleep 5
- fi
- #
- fi
-
- echo "Leaving rc.local..."
-
-There are a few things to notice about the above:
-
- o When run, 'ntpdate' forces your clock to the time returned by the
- host(s) specified by <host.domain> (you'll need to replace this
- be the IP address(es) of your timehosts. This is good since it gets
- things close to start off with. You can use more than one time
- server.
-
- o 'tickadj' is also called. This does two things: changes the
- default value of 'tick' (which the the amount of time, in ms, that
- is added to the clock every 1/60 seconds) and changes the value
- of 'tickadj' which the the amount that is added or subtracted
- from 'tickadj' when adjtime() is called.
-
- Now Mac clocks are pretty bad and tend to be slow. Sooo, instead of
- having A/UX add the default of 16666ms every 1/60th of a second, you
- may want it to add more (or less) so that it keeps better time. The
- above value works for me but your "best" value may be different and
- will likely require some fooling around to find the best value. As a
- general rule of thumb, if you see 'xntpd' make a lot of negative clock
- adjustments, then your clock is fast and you'll need to _decrease_
- the value of 'tick'. If your adjustments are positive, then you need
- to increase 'tick'. To make a guess on how fast/slow your clock is,
- use 'ntpdate' to sync your clock. Now watch 'xntpd' and see how it
- operates. If, for example, it resets your clock by 1 second every 30
- minutes, then your clock is (1/(30*60)) is about 0.056% off and you'll
- need to adjust 'tick' by 16666*0.00056 or about 9 (i.e. 'tick' should
- be ~16675 if slow or ~16657 if fast)
-
- A/UX's default value of 'tickadj' is 1666 which is too big for
- 'xntpd'... so it also needs to be adjusted. I like using larger
- values then the recommended value of 9 for 'tickadj' (although not
- anything near as big as 1666) since this allows for quick slews
- when adjusting the clock. Even with semi-large values of 'tickadj'
- (~200), getting 5ms (1/200 s) accuracy is easy.
-
-
-Finally, before A/UX and 'xntpd' will work happily together, you need to
-patch the kernel. This is due to the fact that A/UX attempts to keep the
-UNIX-software clock and the Mac-hardware clock in sync. Neither the h/w or
-the s/w clock are too accurate. Also, 'xntpd' will be attempting to adjust
-the software clock as well, so having A/UX muck around with it is asking
-for headaches. What you therefore need to do is tell the kernel _not_ to
-sync the s/w clock with the h/w one. This is done using 'adb'. The
-following is a shell script that will do the patch for you:
-
- #! /bin/sh
- adb -w /unix <<!
- init_time_fix_timeout?4i
- init_time_fix_timeout?w 0x4e75
- init_time_fix_timeout?4i
- $q
- !
-
-This must be done _every_ time you create a new kernel (via newconfig or
-newunix) or else 'xntpd' will go crazy.
-
---------
-HISTORY:
---------
-
-John Dundas was the original porter of 'xntpd' and a lot of the additions
-and A/UX-ports are from him. I got involved when I wanted to run 'xntpd'
-on jagubox. It was also around this time that the base-patchlevel of
-'xntpd' changed relatively (the so-called "jones" version). Since then,
-I've been maintaining 'xntpd' for A/UX for the xntp development team
-
-The original kernel patch (which patched 'time_fix_timeout') was from
-Richard Todd. I suggest patching 'init_time_fix_timeout' which prevents
-'time_fix_timeout' from even being called.
-
-----------------
-TECHNICAL NOTES:
-----------------
-
- o As configured (see machines/aux3), 'xntpd' will log messages via syslogd
- using the LOC_LOCAL1 facility. I would suggest the following in
- /etc/syslog.conf:
-
- local1.notice /usr/adm/ntpd-syslog
-
- o As mentioned above, the clocks on A/UX and Macs are kinda bad. Not
- only that, but logging in and out of the MacOS mode as well as
- extensive floppy use causes A/UX to drop and lose clock interupts
- (these are sent every 1/60th of a second). So, if you do these
- activities a lot, you find out that you lose about 300ms of time
- (i.e., you become 300ms slow). 'xntpd' default way of handling this
- is to called 'settimeofday()' and step the clock to the correct
- time. I prefer having 'xntpd' slew the clock back into line by
- making gradual adjustments to the clock over a coupla minutes
- or so. It's for this reason that SLEWALWAYS is defined in
- include/ntp_machine.h for SYS_AUX3. It's also for this reason than
- I like larger values of 'tickadj'.
-
-Good luck! If you have problems under A/UX feel free to contact me (e-mail
-is preferred).
---
- Jim Jagielski | "That is no ordinary rabbit... 'tis the
- jim@jagubox.gsfc.nasa.gov | most foul, cruel and bad-tempered
- NASA/GSFC, Code 734.4 | rodent you ever set eyes on"
- Greenbelt, MD 20771 | Tim the Enchanter
diff --git a/html/build/hints/aix b/html/build/hints/aix
deleted file mode 100644
index e53befff21bb..000000000000
--- a/html/build/hints/aix
+++ /dev/null
@@ -1,76 +0,0 @@
-Problem with recent ANSI compilers
-
-On some systems, including AIX, the compiler quits on the ntp_refclock.c
-file when processing the refclock_report() routine. The problem, which
-is eithre a feature or a bug, has to do with an unwanted promotion of
-the u_char argument to an int and a failure of the compiler to recognize
-the preceding prototype. A workaround is to use ANSI syntax to delare
-the arguments. Since ANSI compilers are not universally available, this
-syntax can't be used in the stock distribution.
-
-(Message # 60: 2884 bytes, New)
-Date: Sat, 19 Aug 1995 13:20:50 -0400
-From: "R. Bernstein" <rocky@panix.com>
-Newsgroups: comp.protocols.time.ntp
-to: mills@udel.edu
-return-receipt-to: rocky@panix.com
-Subject: time and AIX 3.2.5 raw tty bug
-
-This posting isn't strictly about NTP, any program that may stop the
-clock or set the clock backwards is subject to the AIX 3.2.5 bug.
-
-On AIX 3.2.5, there is a bug in the tty driver for a raw device which
-may crash the box under certain conditions: basically a read() on a
-raw tty in effect, a character was read but not as many as specified
-by VMIN when a read timeout occurred. VTIME specifies the timeout. See
-the AIX manual page on termios.h or that include file. for Information
-on VMIN (or MIN) VTIME (or TIME).
-
-A remedy other than to not use raw tty's is to apply patch U435110.
-
-Details of the problem report follow.
-
-> ABSTRACT:
-> IX43779: TRAP IN PSX_TIMEO
->
-> ORIGINATING DETAILS:
-> Stacktrace shows:
-> IAR: 01460214 posixdd:psx_timeo + 8bf4: ti 4,r12,0x0
-> *LR: 014601a0 posixdd:psx_timeo + 8b80
-> 00212c60: 014604f4 posixdd:psx_timer + 8ed4
-> 00212cc0: 0144b74c ttydd:tty_do_offlevel + 4284
-> 00212d20: 000216fc .i_offlevel + 8c
-> 00212d70: 00021d78 .i_softint + c8
-> 00001004: 00008714 .finish_interrupt + 80
->
-> RESPONDER SUMMARY:
-> AIX asserted in psx_timeo(). Reason for the assert was that
-> the current time was behind psx_ctime. Since this state
-> can occur when the current time is changed after a character
-> is received but before the VTIME interbyte timer pops, we
-> should not assert on this.
->
-> RESPONDER CONCLUSION:
-> Removed the requirement that current time > psx_ctime by
-> adding a new L_ntimersub macro that is used instead of the
-> ntimersub macro in time.h. Also added a test for (current
-> time - psx_ctime) being negative, in that case we do not
-> adjust the new timeout.
->
-> Reported to Correct a PTF in Error: NO
-> Reported as a Highly pervasive problem: NO
->
-> PE Apar?: NoPE
-> Hiper Apar?: NoHiper
-> Status: CLOSED PER
-> Component Name: AIX V3 FOR RS/6
-> Version: 320
-> Component ID: 575603001
-> Submitted: 94/05/03
-> Closed: 94/05/05
-> ChangeTeam: TX2527
->
-> APAR FIXED BY: U431696 U432151 U432844 U432870 U432979
-> U433049 U433081 U433459 U433876 U433906 U434598 U434453
-> U434672 U434737 U435110
-
diff --git a/html/build/hints/bsdi b/html/build/hints/bsdi
deleted file mode 100644
index 3b8bc386efea..000000000000
--- a/html/build/hints/bsdi
+++ /dev/null
@@ -1,65 +0,0 @@
-hints/bsdi
-
-Author: Bdale Garbee, bdale@gag.com
-Last revision: 27Oct94 (Paul Vixie)
-
-Included in this distribution of XNTP is a configuration file suitable
-for use with BSDI's BSD/OS 1.1 (formerly BSD/386 1.1). On this system,
-the "cc" command is GCC 1.4x rather than PCC or GCC 2.x. It is imperative
-that "cc" be used since it predefines the symbol __bsdi__; if you want to
-use another compiler you will need to add -D__bsdi__ to catch the various
-#ifdef's required for this system.
-
-The Kinemetrics/Truetime GPS-TM/TMD driver is known to work on this system.
-The GPS-805 and GOES should also work fine. Hell, they should all work fine
-but it's hard to test very many locally.
-
-Due to BNR2's strict interpretation of POSIX and XNTP's use of SIGIO, BSD/OS
-can only handle one refclock per daemon. We're working this out with the
-system architects.
-
-The config file is machine/bsdi, and the following steps should be all that
-are required to install and use the bits.
-
-Note that you will need GNU sed; the version supplied with BSD/OS 1.1 loops
-endlessly during "make refconf". Likewise you should get GNU make, which
-the instructions below assume that you have put in /usr/local/bin/gnumake.
-
-To build the software:
-
- rm -f Config.local
- gnumake refconf
- gnumake MAKE=gnumake
-
-To install the software:
-
- gnumake install
-
- This will place all of the executables in /usr/local/etc. The config
- file is expected to be /usr/local/etc/xntp.conf and the key file for
- the optional authentication is /etc/ntp.keys.
-
- Craft a config file and a key file, and put them in the right places.
- There is information on how to do this elsewhere in the documentation,
- the only thing I'll mention is that I put the drift file in
- /var/log/ntp.drift, and the authdelay on my 486DX/50 system is
- 0.000064. Your mileage will vary, learn to use the authspeed tools
- if you're going to authenticate.
-
- In the file /etc/rc.local, make sure that the invocation of ntpd is
- commented out, and add an invocation of xntpd. Here's what I'm using:
-
- echo -n 'starting local daemons:'
-
- if [ -f /etc/ntp.keys -a -f /usr/local/etc/xntp.conf ]; then
- echo -n ' xntpd'; /usr/local/etc/xntpd
- fi
-
- #XXX# echo -n ' ntpd'; /usr/libexec/ntpd -t
-
-At this point, you should be good to go. Try running /usr/local/etc/xntpd and
-using ntpq or xntpdc to see if things are working, then pay attention the next
-time you reboot to make sure that xntpd is being invoked, and use ntpq or
-xntpdc again to make sure all is well.
-
-Enjoy!
diff --git a/html/build/hints/changes b/html/build/hints/changes
deleted file mode 100644
index 177e562b6dc6..000000000000
--- a/html/build/hints/changes
+++ /dev/null
@@ -1,13 +0,0 @@
-Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> (xntpd/refclock_parse.c):
- - Added support to supply power from RS232 with CLOCK_RAWDCF.
- Known to work with Linux 1.2.
- - Made Linux ignore parity errors with CLOCK_RAWDCF.
-
-Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> (parse/util/dcfd.c):
- - Removed conflicting prototype for Linux (sscanf)
- - Corrected spelling error
- - Made Linux ignore parity errors.
- - Added support to supply power from RS232 with CLOCK_RAWDCF.
-
-Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> (parse/util/testdcf.c):
- - Made Linux ignore parity errors.
diff --git a/html/build/hints/decosf1 b/html/build/hints/decosf1
deleted file mode 100644
index bc4ce0bb294d..000000000000
--- a/html/build/hints/decosf1
+++ /dev/null
@@ -1,40 +0,0 @@
-Some major changes were necessary to make xntp v3 run on the DEC Alpha
-hardware running DEC OSF/1. All "long" and "u_long" declarations and
-casts in the code were changed to "LONG" and "U_LONG" and a new header
-file (include/ntp_types.h) was added. The new header file defines
-LONG as int and U_LONG as u_int for the Alpha hardware and as long
-and u_long for anything else. A couple of #ifs where changed in
-ntpq and xntpdc to get the result of a signal defined correctly. The
-Config.decosf1 file built the programs here with no problems.
-
-I don't have a radio clock here, so none of that code has been tested.
-I have run xntpd, xntpdc, xntpres, ntpq, ntpdate, and tickadj under
-DEC OSF/1 v1.2-2 (BL10).
-
-Mike Iglesias Internet: iglesias@draco.acs.uci.edu
-University of California, Irvine BITNET: iglesias@uci
-Office of Academic Computing uucp: ...!ucbvax!ucivax!iglesias
-Distributed Computing Support phone: (714) 856-6926
-
-Support for NTP Version 2 is included with the current OSF/1 release. If
-you are upgrading to NTP Version 3 with this distribution, you should not
-use the xntpd or ntpq programs that come with the OSF/1 release. The
-older programs should be replaced by the newer programs of the same name,
-either in situ or via a link to a tranquil spot like /usr/local/bin. The
-make install script in the this distribution don't work due to a silly
-install program incompatibility, so you will need to copy the programs by
-hand.
-
-Don't use the setup utility to install or configure the xntpd installation,
-as it will cheerfully clobber your painstakingly crafted ntp.conf program.
-However, assuming you put this file in /etc/ntp.conf, you can use the
-/sbin/init.d/xntpd script to start and stop the daemon.
-
-This distribution compiles with nominal mumur with the stock cc compiler
-that comes with OSF/1.
-
-Dave Mills
-Electrical Engineering Department
-Unibergisty of Delabunch
-mills@udel.edu
-
diff --git a/html/build/hints/decosf2 b/html/build/hints/decosf2
deleted file mode 100644
index e4a8828cc508..000000000000
--- a/html/build/hints/decosf2
+++ /dev/null
@@ -1,54 +0,0 @@
-Problems with DEC OSF/1 V2.0
-
-Compilation using gcc fails with ntp_config.c. The problem is an apparent
-error in the /usr/include/sys/procset.h and /usr/include/sys/wait.h
-include files.
-
-cowbird:/usr/include/sys# diff -c wait.h.orig wait.h
-*** wait.h.orig Tue Feb 22 02:41:38 1994
---- wait.h Thu Aug 25 14:52:57 1994
-***************
-*** 298,304 ****
- #else
-
- _BEGIN_CPLUSPLUS
-! extern int waitid(idtype_t, id_t, siginfo_t *, int);
- _END_CPLUSPLUS
- #endif /* _NO_PROTO */
-
---- 298,304 ----
- #else
-
- _BEGIN_CPLUSPLUS
-! extern int waitid(idtype_t, pid_t, siginfo_t *, int);
- _END_CPLUSPLUS
- #endif /* _NO_PROTO */
-
-cowbird:/usr/include/sys# diff -c procset.h.orig procset.h
-*** procset.h.orig Tue Feb 22 02:41:44 1994
---- procset.h Thu Aug 25 14:43:52 1994
-***************
-*** 86,95 ****
- */
-
- idtype_t p_lidtype; /* The id type for the left set. */
-! id_t p_lid; /* The id for the left set. */
-
- idtype_t p_ridtype; /* The id type of for right set. */
-! id_t p_rid; /* The id of the right set. */
- } procset_t;
-
-
---- 86,95 ----
- */
-
- idtype_t p_lidtype; /* The id type for the left set. */
-! pid_t p_lid; /* The id for the left set. */
-
- idtype_t p_ridtype; /* The id type of for right set. */
-! pid_t p_rid; /* The id of the right set. */
- } procset_t;
-
-Also, if using gcc from the freeware disk, either replace syscall.h
-in the directory /usr/local/lib/gcc-lib/alpha-dec-osf1/2.3.3/include
-or replace with a link to /usr/include/sys/syscall.h.
diff --git a/html/build/hints/freebsd b/html/build/hints/freebsd
deleted file mode 100644
index ef847328bb3d..000000000000
--- a/html/build/hints/freebsd
+++ /dev/null
@@ -1,15 +0,0 @@
-If you are compiling under FreeBSD and see messages in the syslogs that
-indicate that the ntpd process is trying to use unavailable sched_
-calls, it means you are running a kernel that does not have the POSIX
-scheduling calls enabled.
-
-You have two choices:
-
-- Ignore the messages
-
-- Generate a new kernel, where the kernel configuration file contains
- the lines:
-
- options "P1003_1B"
- options "_KPOSIX_PRIORITY_SCHEDULING"
- options "_KPOSIX_VERSION=199309L"
diff --git a/html/build/hints/hpux b/html/build/hints/hpux
deleted file mode 100644
index 1640d057a350..000000000000
--- a/html/build/hints/hpux
+++ /dev/null
@@ -1,158 +0,0 @@
-Last update: Sun Mar 13 15:05:31 PST 1994
-
-This file hopefully describes the whatever and however of how to get xntp
-running on hpux 7.0 and later s300. s400, s700, and s800.
-
-First off, all the standard disclaimers hold here ... HP doesn't have anthing
-to do with this stuff. I fool with it in my spare time because we use it and
-because I like to. We just happen to have a lot of HP machines around here :-)
-Xntpd has been in use here for several years and has a fair amount of mileage
-on various HP platforms within the company. I can't really guarantee bug fixes
-but I'd certainly like to hear about bugs and I won't hestitate to look at
-any fixes sent to me.
-
-Now lets talk OS. If you don't have 7.0 or later, pretty much hang it up now.
-This stuff has run here on pretty much everything from 8.0 upward on s300,
-s700, and s800. It is known to run on 7.0 s300/s400 but all reports are
-from the field and not my personal experience.
-
-If you are lucky enough to have a s300 or s400 with 9.03, then you no longer
-have to worry about adjtimed as HP-UX now has adjtime(2). The rest of you
-will have to wait on 10.0 which will have adjtime(2) and a supported though
-a bit older version of xntpd.
-
-Next, let me explain a bit about how this stuff works on HP-UX's that do not
-have adjtime(2). The directory adjtime contains libadjtime.a and the adjtimed
-daemon. Instead of the adjtime(2) system call, we use a library routine to
-talk to adjtimed thru message queues. Adjtimed munges into /dev/kmem and
-causes the clock to skew properly as needed. PLEASE NOTE that the adjtime
-code provided here is NOT a general replacement for adjtime(2) ... use of
-this adjtime(3)/adjtimed(8) other than with xntpd may yield very odd results.
-
-What to do to get this stuff running ?
-
- * If you are running an OS less than 10.0 or do not have a s300/s400
- with 9.03 or better
- -> cd machines
- -> vi hpux
- -> (change -DSYS_HPUX=? to match whatever you are running [7,8,9])
- -> cd ..
-
- * Say "make makeconfig"
-
- * Say "make", sit back for a few minutes.
-
- * cd authstuff
- * Say "./authcert < certdata" and check the output. Every line should
- end with "OK" ... if not, we got trouble.
- * Now try "./authspeed auth.samplekeys". What we want to
- remember here is the "authentication delay in CPU time"
- * cd ..
-
- * Say "make install"
-
- * I'd suggest reading the xntp docs about now :-) ... seriously !!
-
- * One thing I have added to this version of xntpd is a way to select
- config files if you are sharing /usr/local thru NFS or whatever.
- If the file /usr/local/etc/xntp.conf happens to be a directory, the
- files in that directory are searched until a match is found. The
- rules for a match are:
-
- 1. Our hostname
- 2. default.<machine id> (as in default.375 or default.850)
- 3. default
-
- * Ok, make sure adjtimed is running (just start it up for now with
- "/usr/local/etc/adjtimed"). Using -z as an option will get you
- a usage message.
-
- * Now start up xntpd and watch it work.
-
- * Make sure that adjtimed gets started at boot right before xntpd.
- We do this in /etc/netbsdsrc. They must both run as root !!
-
-Possible problems ?
-
- * On some 320's and 835's we have had to run adjtimed with "-p 45" or
- so to get rid of syslog messages about "last adjust did not finish".
-
- * At 9.0, there is a problem with DIAGMON (patch available from the
- response center) which causes it to delete the message queue that
- adjtimed/xntpd use to communicate. (see next note for result)
-
- * Xntpd has been known to get really ticked off when adjtime() fails
- which is usually only while running the emulation code on HP-UX.
- When it gets mad, it usually jumps the clock into never never land.
- Possible reasons for this are adjtimed being killed or just never
- started or adjtimed being completely swapped out on a really busy
- machine (newer adjtimed try to lock themselves in memory to prevent
- this one).
-
-Anything else ... just drop me a line at ken@sdd.hp.com
-
-Received: from louie.udel.edu by huey.udel.edu id aa14418; 15 Jun 95 9:19 EDT
-Received: from host5.colby.edu (host-05.colby.edu) by host-04.colby.edu with ESMTP (1.37.109.15/Colby 1.1)
- id AA165442355; Thu, 15 Jun 1995 09:19:16 -0400
-Received: by host5.colby.edu (1.37.109.15/Colby 1.1)
- id AA056252339; Thu, 15 Jun 1995 09:18:59 -0400
-Date: Thu, 15 Jun 1995 09:18:59 -0400 (EDT)
-From: "Jeff A. Earickson" <jaearick@colby.edu>
-To: Mills@huey.udel.edu
-Subject: More minor bugs in xntp3.4s
-In-Reply-To: <9506150022.aa12727@huey.udel.edu>
-Message-Id: <Pine.HPP.3.91.950615083549.4557A-100000@host5.colby.edu>
-Mime-Version: 1.0
-Content-Type: TEXT/PLAIN; charset=US-ASCII
-
-Dave,
- After reading the hpux hints file, I realized I didn't install or
-start adjtimed. In the course of doing this, I discovered that:
-
---> $(TOP) is not defined in adjtime/Makefile, so "make install" can't
- find the install.sh script.
-
---> "make install" from the main Makefile never goes into the adjtime
- directory, so I added the following two lines into the install
- target of the main Makefile:
-
- @echo installing from adjtime
- @cd adjtime && $(MAKE) $(MFLAGS) MFLAGS="$(MFLAGS)" MAKE="$(MAKE)" install
-
-This twiddle may not be right for all systems, but it got adjtimed
-installed for me.
-
- You might also want to add to the hpux hints file that one way to
-fire things up at boot time is to add the following lines to the localrc
-function of /etc/rc:
-
- #---daemons for Network Time Protocol (version 3.4s)
- #---note that adjtimed is only needed for HP-UX 9.X, not 10.0
- #---adjtimed must be running or xntpd won't work right...
- if [ -x /usr/local/bin/adjtimed ]; then
- /usr/local/bin/adjtimed -r & echo -n ' adjtimed'
- if [ -x /usr/local/bin/xntpd ]; then
- /usr/local/bin/xntpd & echo -n ' xntpd'
- fi
- fi
-
-I discovered that the "-r" option of adjtimed is needed to clear out any
-trash from a previous execution of it. Otherwise adjtimed quietly dies
-and leaves xntpd in the lurch...
-
-Thanks for the help.
-
-** Jeff A. Earickson, Ph.D PHONE: 207-872-3659
-** Senior UNIX Sysadmin, Information Technology EMAIL: jaearick@colby.edu
-** Colby College, 4214 Mayflower Hill, FAX: 207-872-3555
-** Waterville ME, 04901-8842
-
-On Thu, 15 Jun 1995 Mills@huey.udel.edu wrote:
-
-> Jeff,
->
-> Read the hpux file in the hints directory.
->
-> Dave
->
-
diff --git a/html/build/hints/linux b/html/build/hints/linux
deleted file mode 100644
index b06a36a63465..000000000000
--- a/html/build/hints/linux
+++ /dev/null
@@ -1,5 +0,0 @@
-The kernel PLL interface is broken, I know.
-Update RSN.
-
- Torsten
- (duwe@informatik.uni-erlangen.de)
diff --git a/html/build/hints/mpeix b/html/build/hints/mpeix
deleted file mode 100644
index 83c7241e04bb..000000000000
--- a/html/build/hints/mpeix
+++ /dev/null
@@ -1,50 +0,0 @@
-HP e3000 MPE/iX NTP Hints - May 29, 2001
-----------------------------------------
-
-NTP was first ported to MPE several years ago, but those diffs were never
-submitted back to the official NTP distribution. For more information about
-that deprecated port, please see http://www.bixby.org/mark/xntpix.html.
-
-NTP was re-ported to MPE in May 2001. What follows are hints learned from
-working with NTP 4.0.99k23. For additional information about NTP on MPE,
-please see http://jazz.external.hp.com/src/hp_freeware/ntp/.
-
-MPE lacks the clock-related APIs expected by NTP, so adjtime(), gettimeofday(),
-and settimeofday() all had to be implemented from scratch by calling
-privileged, undocumented internal OS functions.
-
-Unfortunately the implementation of adjtime() has exposed a sub-second accuracy
-bug when slewing the system time. This bug is documented in SR 5003462838, and
-exists on all current versions of MPE. It has not been fixed at the time of
-this writing. The adjtime() code may possibly need to be altered if/when this
-bug is fixed.
-
-This bug has a side-effect whereby the ntpd daemon will screw up the hardware
-PDC clock time by many minutes if used for continuous clock adjustments or in
-the one-time -q mode. But note that you can safely run ntpd in order to become
-a time server if you include "disable ntp" in the ntp.conf configuration file.
-
-The one-time clock adjustment functionality of ntpdate and ntp_timeset is not
-affected by this bug side-effect. You can safely use these commands to alter
-your system time with reasonable accuracy.
-
-The only reference clock that has been tested on MPE is the local clock. So
-building NTP with --disable-all-clocks --enable-LOCAL_CLOCK is strongly
-recommended.
-
-NTP makes use of Privileged Mode (PM) capability in order to bind to the NTP
-network port (123) and to access the low-level clock functions.
-
-NTP was ported using the gcc compiler. Attempting to use the HP C/iX compiler
-is not recommended and has not been tested.
-
-Please note that NTP is not an HP product and is NOT supported by HP. The best
-place for asking MPE-specific questions about NTP is the HP3000-L mailing list
-at http://raven.utc.edu/Archives/hp3000-l.html or the associated Usenet
-newsgroup of comp.sys.hp.mpe.
-
-The original author of this port is:
-
-Mark Bixby
-HP CSY MPE Internet & Interoperability Engineer
-mark_bixby@hp.com
diff --git a/html/build/hints/netbsd b/html/build/hints/netbsd
deleted file mode 100644
index f5f628db4590..000000000000
--- a/html/build/hints/netbsd
+++ /dev/null
@@ -1,37 +0,0 @@
-Starting with NetBSD-1.6, it is possible to delegate the system clock
-control to a non root user. This enable running ntpd in a chroot
-jail under a non privilegied UID/GID, using ntpd -i and -u flags.
-
-The delegation is done through the clockctl(4) pseudodevice driver.
-This driver makes privilegied system calls such as ntp_adjtime(2)
-available through ioctl(2) on the /dev/clockctl device. If a user
-is able to write to /dev/clockctl, then (s)he can control the system
-clock.
-
-In order to use this feature, make sure that:
-
-1) Your kernel is compiled with the following option:
-pseudo-device clockctl
-This is true for GENERIC kernels on most ports. Please check
-http://wwW.netbsd.org/Documentation/kernel/
-if you need information about building a kernel.
-
-2) You have a ntpd user on your system. Here is the /etc/master.passwd
-entry for ntpd user on NetBSD-1.6:
-ntpd:*:15:15::0:0:& pseudo-user:/var/chroot/ntpd:/sbin/nologin
-And here is the /etc/group entry for group 15:
-ntpd:*:15:
-
-3) /dev/clockctl exists and is writtable by user ntpd. Default
-NetBSD-1.6 setting is:
-crw-rw---- 1 root ntpd 61, 0 Apr 1 2002 /dev/clockctl
-Major device number and date is likely to be different on your system.
-If you need to create the device, issue the following command:
-cd /dev && ./MAKEDEV clockctl
-
-Here is an example of how to run ntpd chrooted in /var/chroot/ntpd,
-running with ntpd UID and ntpd GID:
-ntpd -i /var/chroot/ntpd -u ntpd:ntpd
-Note that -i and -u options are enabled at configure time if your
-system supports system clock control by an unprivilegied user. If this
-is not the case, then the -i and -u options will not be available.
diff --git a/html/build/hints/notes-xntp-v3 b/html/build/hints/notes-xntp-v3
deleted file mode 100644
index ba027f2105fe..000000000000
--- a/html/build/hints/notes-xntp-v3
+++ /dev/null
@@ -1,119 +0,0 @@
-Notes for NTP Version 3
-
-This version operates in much the same manner as Version 2 with the
-following changes and additions:
-
-1. The protocol machinery operates in conformance with the RFC1305 NTP
- Version 3 specification. The most visible characteristic of this
- version is that the poll intervals for all polls, even selected
- ones, is significantly increased. This is especially desirable when
- serving a large client population. This implementation supports
- previous versions as non-configured peers; for version-2 configured
- peers a "version 2" keyword should be included on the "peer" line.
-
-2. The configuration file has a new keyword: statfile <file>, where
- <file> is the name of a statistics file." When present, each clock
- update generates an entry of the form:
-
- <day> <sec>.<frac> <addr> <status> <offset> <delay> <disp>
-
- where <day> is the modified Julian day, <sec>.<frac> is the time of
- day, <addr> is the peer address and <status> is the peer status.
- The <offset>, <delay> and <disp> are the measured offset, delay and
- dispersion, respectively, of the peer clock relative to the local
- clock. About once per day the current file is closed and a new one
- created with names <file>.<gen>, where <gen> starts at one and
- increments for each new generation.
-
-3. A number of additional platforms are supported. See ./Config file
- for details.
-
-4. A driver for the TrueTime 468DC GOES Synchronized Clock is
- included. This driver (refclock_goes.c) should also work for other
- TrueTime radio clocks, since all use the same format.
-
-5. A replacement driver for the Spectracom 8170 WWVB Synchronized
- Clock is included. This driver (refclock_wwvb.c) (a) does not
- require a 1-pulse-per-second signal, (b) supports both format 0
- (original 8170) and format 2 (Netclock/2 and upgraded 8170), (c)
- can be connected to more than one computer and (d) automatically
- compensates for all serial baud rates.
-
-6. A driver for the German time/frequency station DCF77 is included.
- This requires a special STREAMS module.
-
-7. In Version 2 special line-discipline modules were required for the
- CHU and WWVB drivers. This code continues to work in Version 3,
- although it is no longer needed for the WWVB driver. However, this
- code does not work under STREAMS, as used in SunOS 4.1.1.
- Equivalent STREAMS modules are supplied with Version 3.
-
-8. Support for an external 1-pulse-per-second (pps) signal is
- provided. The signal is connected to a serial port (see
- xntpd/ntp_loopfilter.c for details). When present the leading edge
- of the pulse establishes the on-time epoch within an interval
- established by the selected radio clock or other NTP time server.
- Use of the pps is indicated when the tattletale displayed by ntpq
- changes from "*" to "o".
-
-9. The clock-selection and poll-update procedures have been modified
- slightly in order to achieve better performance on high speed LANs
- with compromise in performance on typical WANs.
-
-10. In order to comply with U.S. Commerce Department regulations, the DES
- encryption routine lib/authdes.c cannot be exported. For exportable
- versions of this distribution a DES-encrypted version of this routine
- lib/authdes.c.des is included along with an unencrypted version
- lib/authdes.c.export, which allows normal operation, but without the
- NTP authentication feature. Further information is available in the
- lib/authdes.c.export file.
-
-11. As an alternative to the DES-based authentication mechanism, an
- implementation of the RSA Message Digest 5 algorithm is provided.
- (see applicable copyright information in the library files).
-
-12. A driver for the Magnavox MX4200 GPS clock.
-
-13. A STREAMS module which captures carrier-detect data-lead transitions to
- connect a precision source of 1-pps, yet avoid the ugly overhead in the
- usual STREAMS processing. See the ppsclock subdirectory.
-
-14. Support for the Apple A/UX operating system and enhanced support for the
- Hewlet-Packard HP/UX operating system. See the various README and Config
- files for further information.
-
-See the COPYRIGHT file for authors and copyright information. Note that some
-modules in this distribution contain copyright information that supersedes
-the copyright information in that file.
-
-If I missed something or neglected to give due credit, please advise.
-
-David L. Mills
-University of Delaware
-31 May 1992, amended 23 July 1992, 25 October 1992
-
-Bugs and notes
-
-A bug in the original tty_clk_STREAMS.c module has been fixed.
-
-The poll-interval randomization feature of poll_update (in
-xntpd/ntp_proto.c) has been extended to apply when the poll interval is
-increased, as well as reduced. This spreads the update messages in time
-and helps avoid unpleasant bursts of messages.
-
-In the clock_select algorithm the peers selected for combining are
-limited to those survivors at the lowest stratum, not the entire list.
-This helps avoid whiplash when large numbers of peers are at the same
-stratum.
-
-The number formerly displayed by ntpq as "compliance" is now the time
-constant of integration.
-
-The DNS resolver xntpd/ntp_intres.c is now integrated into xntpd, making
-configuration of multiple hosts easier.
-
-System and peer event are now written to the system log at priority
-LOG_INFO.
-
-The leap-second code was fixed to avoid broadcasting leap warnings on
-all except the last day of June and December.
diff --git a/html/build/hints/parse b/html/build/hints/parse
deleted file mode 100644
index 07fbc6bfeec2..000000000000
--- a/html/build/hints/parse
+++ /dev/null
@@ -1,105 +0,0 @@
-Compilation:
- Usual thing: rm -f Config.local ; make for vanilla
- make refconf for reference clock (e. g. DCF77)
-
-Directory contents:
-
- hints/PARSE - this file
-
- xntpd/refclock_parse.c
- - reference clock support for DCF77/GPS in xntp
- parse/parse.c
- - Reference clock data parser framework
- parse/parse_conf.c
- - parser configuration (clock types)
- parse/clk_meinberg.c
- - Meinberg clock formats (DCF U/A 31, PZF 535, GPS166)
- parse/clk_schmid.c
- - Schmid receiver (DCF77)
- parse/clk_rawdcf.c
- - 100/200ms pulses via 50 Baud line (DCF77)
- parse/clk_dcf7000.c
- - ELV DCF7000 (DCF77)
- parse/clk_trimble.c
- - Trimble SV6 GPS receiver
-
- If you want to add new clock types please check
- with kardel <AT> informatik.uni-erlangen.de. These files
- implement the conversion of RS232 data streams into
- timing information used by refclock_parse.c which is
- mostly generic except for NTP configuration constants.
-
- parse/Makefile.kernel
- - *SIMPLE* makefile to build a loadable STREAMS
- module for SunOS 4.x / SunOS 5.x systems
-
- parse/parsestreams.c
- - SUN Streams module (loadable) for radio clocks
- This streams module is designed for SunOS 4.1.X.
-
- parse/parsesolaris.c
- - SUN Streams module (loadable) for radio clocks.
- This streams module is designed for SunOS 5.x
- Beware this is still new - so it might crash
- your machine (we have seen it working, though).
-
- parse/parsetest.c
- - simple test program for STREAMS module. Its so simple,
- that it doesn't even set TTY-modes, thus they got to
- be correct on startup - works for Meinberg receivers
-
- parse/testdcf.c
- - test program for raw DCF77 (100/200ms pulses)
- receivers
-
- include/parse.h - interface to "parse" module and more
- include/parse_conf.h
- - interface to "parse" configuration
-
- include/sys/parsestreams.h
- - STREAMS specific definitions
-
- scripts/support
- - scripts (perl & sh) for statistics and rc startup
- the startup scripts are used in Erlangen for
- starting the daemon on a variety of Suns and HPs
- and for Reference Clock startup on Suns
- These scripts may or may not be helpful to you.
-
-Supported clocks:
- Meinberg DCF U/A 31
- Meinberg PZF535/TCXO (Software revision PZFUERL 4.6)
- Meinberg PZF535/OCXO (Software revision PZFUERL 4.6)
- Meinberg GPS166 (Software version for Uni-Erlangen)
- ELV DCF7000 (not recommended - casual/emergency use only)
- Conrad DCF77 receiver (email: time@informatik.uni-erlangen.de)
- + level converter
- TimeBrick (email: time@informatik.uni-erlangen.de)
- Schmid Receiver Kit
- Trimble SV6 GPS receiver
-
-Addresses:
- Meinberg Funkuhren
- Auf der Landwehr 22
- 31812 Bad Pyrmont
- Germany
- Tel.: 05281/20 18
- FAX: 05281/60 81 80
-
- ELV Kundenservice
- Postfach 1000
- 26787 Leer
- Germany
- Tel.: 0491/60 08 88
-
- Walter Schmidt
- Eichwisrain 14
- 8634 Hombrechtikon
- Switzerland
-
-If you have problems mail to:
-
- time@informatik.uni-erlangen.de
-
-We'll help (conditions permitting)
-
diff --git a/html/build/hints/refclocks b/html/build/hints/refclocks
deleted file mode 100644
index 17e76434a307..000000000000
--- a/html/build/hints/refclocks
+++ /dev/null
@@ -1,35 +0,0 @@
-This is a short overview for the reference clocks currently supported
-by xntp V3. (Ultimate wisdom can be obtained from xntpd/refclock_*.c
-this file was derived from that information - unfortunately some comments
-in the files tend to get stale - so use with caution)
-
-Refclock address Type
-127.127.0.x no clock (fails to configure)
-127.127.1.x local clock - use local clock as reference
-127.127.2.x no clock (fails to configure)
-127.127.3.x PSTI 1010/1020 WWV Clock
-127.127.4.x SPECTRACOM WWVB receiver 8170 and Netclock/2
-127.127.5.x Kinimetric Truetime 468-DC GOES receiver
-127.127.6.x IRIG audio decode (Sun & modified BSD audio driver)
-127.127.7.x CHU Timecode (via normal receiver & Bell 103 modem)
-127.127.8.x PARSE (generic driver for a bunch of DCF/GPS clocks
- can be extended for other clocks too)
- 8.0-3 Meinberg PZF535/TCXO
- 8.4-7 Meinberg PZF535/OCXO
- 8.8-11 Meinberg DCF U/A 31
- 8.12-15 ELV DCF7000
- 8.16-19 Walter Schmid DCF receiver (Kit)
- 8.20-23 Conrad DCF77 receiver module + level converter (Kit)
- 8.24-27 TimeBrick (limited availability ask
- time@informatik.uni-erlangen.de)
- 8.28-31 Meinberg GPS166
- 8.32-35 Trimble SV6 GPS receiver
-127.127.9.x MX4200 GPS receiver
-127.127.10.x Austron 2201A GPS Timing Receiver
-127.127.11.x Kinemetrics Truetime OM-DC OMEGA Receiver
-127.127.12.x KSI/Odetecs TPRO-S IRIG-B / TPRO-SAT GPS
-127.127.13.x Leitch: CSD 5300 Master Clock System Driver
-127.127.14.x MSFEES
-127/127.15.x TrueTime GPS/TM-TMD
-127.127.16.x Bancomm GPS/IRIG Ticktock
-127.127.17.x Datum Programmable Time System
diff --git a/html/build/hints/rs6000 b/html/build/hints/rs6000
deleted file mode 100644
index 8561ac29b1b0..000000000000
--- a/html/build/hints/rs6000
+++ /dev/null
@@ -1,56 +0,0 @@
-15.7.1993
-xntp3 compiles now again on AIX. I have disabled prototyping and added
-the switch -D_NO_PROTO which disables prototyping in the system include
-files.
-
-Matthias Ernst maer@nmr.lpc.ethz.ch
---------------------------------------------------------------------------------
-Xntp version 3 now support the cc compiler for AIX.
-The Config.aix will now use cc by default. You can still compile xntp
-with the bsd compiler by changing "COMP= cc" to "COMP= bsdcc" and
-and removing the "-DSTUPID_SIGNAL" option from the "DEFS" option.
-
-xntp and tickadj was also modified so that the value of tickadj is read
-form the kernel and can be set by tickadj. For now I would not set
-tickadj below 40 us.
-
-Bill Jones
-jones@chpc.utexas.edu
--------------------------------------------------------------------------------
-
-This is a modified version of xntp version 3 for the RS6000. It works for
-AIX 3.2 and these are the same changes as have been applied tothe version 2
-implementation of xntp. It works fine for us but I have not tested all of
-the features, especially the local clock support for the RS6000 is not tested
-at all.
-
-Matthias Ernst, ETH-Zuerich, Switzerland - maer@nmr.lpc.ethz.ch
-
---------------------------------------------------------------------------------
-
-Here the original README.rs6000 for the version 2 implementation:
-
-A hacked version of xntp for the IBM RS/6000 under AIX 3.1 can be found
-in xntp.rs6000.tar.Z. [ if still available at all - Frank Kardel 93/12/3 ]
-
-This will not work on older versions of AIX due to a kernel bug; to find
-out whether you have the kernel bug, compile and run testrs6000.c (see
-comments in the code for instructions).
-
-xntp and testrs6000 require "bsdcc" to compile. This is simply another
-entry point into the xlc compiler with various options set for BSD
-compatibility. If your system does not have bsdcc, do the following:
-
-link /bin/bsdcc to /bin/xlc
-
-put the following into /etc/xlc.cfg:
-
-* BSD compatibility
-bsdcc: use = DEFLT
- crt = /lib/crt0.o
- mcrt = /lib/mcrt0.o
- gcrt = /lib/gcrt0.o
- libraries = -lbsd, -lc
- proflibs = -L/lib/profiled,-L/usr/lib/profiled
- options = -H512,-T512, -qlanglvl=extended, -qnoro, -D_BSD, -D_NONSTD_TYPES, -D_NO_PROTO, -tp,-B/lib/
-
diff --git a/html/build/hints/sco.html b/html/build/hints/sco.html
deleted file mode 100644
index bd08e981bcfc..000000000000
--- a/html/build/hints/sco.html
+++ /dev/null
@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <title>SCO Unix hints</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h1>SCO Unix hints</h1>
- <h2>Older SCO Unix versions</h2>
- <p>NTP 4.0.x does not run on SCO Unix prior to version 3.2.5.0.0. If you need NTP on an older SCO Unix system and don't mind to modify your kernel, use 3.5.91 which has patches for SCO Unix 3.2.4.x. Apply the kernel modifications as described in <a href="http://www.echelon.nl/en/ntp/sco3-recipe.html">XNTP on SCO 3.2.4.2</a>.</p>
- <h2>Compiling NTP</h2>
- <p>Delete the old SCO supplied NTP programs using the &quot;custom&quot; utility. Run the NTP configure program with CFLAGS=&quot;-b elf -K <i>processor-type</i>&quot; for best results.</p>
- <h2>Running NTP</h2>
- <p>Run &quot;tickadj -As&quot; after every reboot to set the variables &quot;clock_drift&quot; and &quot;track_rtc&quot; to the right values.</p>
- <p>Run &quot;ntpd&quot; with a high negative nice-value, i.e. &quot;nice --19 ntpd&quot; for best results.</p>
- <h2>More information</h2>
- <p>More information on the way SCO Unix and NTP interact can be found in <a href="http://www.echelon.nl/en/ntp/ntp-on-sco.html">NTP on SCO Unix</a>, which includes links to precompiled versions of NTP.</p>
- <p><a href="mailto:kees@echelon.nl">Kees Hendrikse</a>, January 1999</p>
- </body>
-
-</html> \ No newline at end of file
diff --git a/html/build/hints/sgi b/html/build/hints/sgi
deleted file mode 100644
index 5e4f7de6d597..000000000000
--- a/html/build/hints/sgi
+++ /dev/null
@@ -1,74 +0,0 @@
-adjtime, tick and tickadj:
---------------------------
-
-The SGI value for HZ is 100 under Irix 4, with the system clock running
-in nominal mode (ftimer off), so the value for tick is 10000 usec.
-Tickadj is a bit more tricky because of the behaviour of adjtime(),
-which seems to try to perform the correction over 100-200 seconds, with
-a rate limit of 0.04 secs/sec for large corrections. Corrections of
-less than 0.017 seconds generally complete in less than a second,
-however.
-
-Some measured rates are as follows:
-
- Delta Rate (sec/sec)
-
- > 1 0.04
- 0.75 0.04
- 0.6 0.004
- 0.5 0.004
- 0.4 0.0026
- 0.3 0.0026
- 0.2 0.0013
- 0.1 0.0015
- 0.05 0.0015
- 0.02 0.0003
- 0.01 0.015
-Strange. Anyway, since adjtime will complete adjustments of less than
-17msec in less than a second, whether the fast clock is on or off, I
-have used a value of 150usec/tick for the tickadj value.
-
-Fast clock:
------------
-
-I get smoother timekeeping if I turn on the fast clock, thereby making
-the clock tick at 1kHz rather than 100Hz. With the fast clock off, I
-see a sawtooth clock offset with an amplitude of 5msec. With it on,
-the amplitude drops to 0.5msec (surprise!). This may be a consequence
-of having a local reference clock which spits out the time at exactly
-one-second intervals - I am probably seeing sampling aliasing between
-that and the machine clock. This may all be irrelevant for machines
-without a local reference clock. Fiddling with the fast clock doesn't
-seem to compromise the above choices for tick and tickadj.
-
-I use the "ftimer" program to switch the fast clock on when the system
-goes into multiuser mode, but you can set the "fastclock" flag in
-/usr/sysgen/master.d/kernel to have it on by default. See ftimer(1).
-
-timetrim:
----------
-
-Irix has a kernel variable called timetrim which adjusts the system
-time increment, effectively trimming the clock frequency. Xntpd could
-use this rather than adjtime() to do it's frequency trimming, but I
-haven't the time to explore this. There is a utility program,
-"timetrim", in the util directory which allows manipulation of the
-timetrim value in both SGI and xntpd native units. You can fiddle with
-default timetrim value in /usr/sysgen/master.d/kernel, but I think
-that's ugly. I just use xntpd to figure out the right value for
-timetrim for a particular CPU and then set it using "timetrim" when
-going to multiuser mode.
-
-Serial I/O latency:
--------------------
-
-If you use a local clock on an RS-232 line, look into the kernel
-configuration stuff with regard to improving the input latency (check
-out /usr/sysgen/master.d/[sduart|cdsio]). I have a Kinemetrics OM-DC
-hooked onto /dev/ttyd2 (the second CPU board RS-232 port) on an SGI
-Crimson, and setting the duart_rsrv_duration flag to 0 improves things
-a bit.
-
-
-12 Jan 93
-Steve Clift, CSIRO Marine Labs, Hobart, Australia (clift@ml.csiro.au)
diff --git a/html/build/hints/solaris-dosynctodr.html b/html/build/hints/solaris-dosynctodr.html
deleted file mode 100644
index fc7fae93550e..000000000000
--- a/html/build/hints/solaris-dosynctodr.html
+++ /dev/null
@@ -1,321 +0,0 @@
-
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-
-
-<!-- Sun Template V4.0 9/9/98 -->
-<HTML>
-<HEAD>
-<TITLE>Symptoms and Resolutions Article 19195</title><link href="scripts/style.css" type="text/css" rel="stylesheet">
-
-<META NAME="GENERATOR" CONTENT="Sun Microsystems, Inc.">
-<META HTTP-EQUIV="content-type" CONTENT="text/html;charset=iso-8859-1">
-
-<!-- INSERT YOUR META TAGS HERE -->
-
-<META NAME="PUBLISHED_DATE" CONTENT="">
-<META NAME="KEYWORDS" CONTENT="">
-<META NAME="DESCRIPTION" CONTENT="">
-
-<!-- END META TAGS -->
-
-<LINK REL="Stylesheet" TYPE="text/css" HREF="/style.css" TITLE="Style">
-
-</HEAD>
-<!--stopindex-->
-<BODY BGCOLOR="#FFFFFF" LINK="#666699" ALINK="#FFFFFF">
-
-
-<TABLE WIDTH="623" BORDER="0">
- <TR>
- <TD COLSPAN="2" VALIGN="TOP" WIDTH="623">
- <IMG BORDER="0" SRC="/images/homebuy.gif" WIDTH="149" HEIGHT="32" ALT="Home * Buy * My Sun(sm)" USEMAP="#lefttop"><IMG BORDER="0" SRC="/images/globalnavbar.gif" WIDTH="474" HEIGHT="32" ALT="sun.com Global Sections" USEMAP="#topnav"></TD>
- </TR>
- <TR>
- <TD COLSPAN="2" VALIGN="TOP" WIDTH="623">
-
- <!-- TITLEBAR IMAGE: INSERT CUSTOMIZED TITLEBAR IMAGE BELOW -->
-
- <A HREF="http://www.sun.com/"><IMG BORDER="0" SRC="/images/sunlogo.gif" WIDTH="149" HEIGHT="72" ALT="Sun Microsystems"></A><IMG BORDER="0" SRC="/images/titlebar/doc.title.gif" alt="gif" WIDTH="474" HEIGHT="72"></TD>
- </TR>
- <!-- Begin Search Elements -->
- <TR VALIGN="top">
- <TD BGCOLOR="#666699">
- <TABLE>
- <TR>
- <TD BGCOLOR="#666699" COLSPAN="2" WIDTH="157" VALIGN="TOP"><IMG BORDER="0" SRC="/images/search/contract/search1.gif" WIDTH="157" HEIGHT="16" ALT="Search SunSolve"></TD>
- </TR>
- <TR>
- <TD VALIGN="top" ALIGN="center" WIDTH="141" BGCOLOR="#666699"><FORM ACTION="search.pl" METHOD="POST"><FONT SIZE="2"><INPUT TYPE="text" NAME="zone_32" SIZE="14"></FONT><input type=hidden name=mode value=results><BR>
-<INPUT TYPE="image" SRC="/images/search/contract/search5.gif" BORDER="0" NAME="Search"><IMG SRC="/images/cg_clear.gif" ALT="" WIDTH="2" HEIGHT="1" BORDER="0" HSPACE="29" VSPACE="0"><BR>
-
-<A HREF="search.pl?mode=advanced"><IMG BORDER="0" SRC="/images/search/contract/search3.gif" WIDTH="144" HEIGHT="16" ALT="Advanced Search"></A><BR>
-
-<A HREF="search.pl?mode=product"><IMG SRC="/images/search/contract/search4.gif" BORDER="0" ALT="Product Search" WIDTH="144" HEIGHT="19"></A><BR>
-
-<A HREF="show.pl?target=help/search_tips"><IMG SRC="/images/search/contract/search6.gif" BORDER="0" ALT="Search Tips" WIDTH="144" HEIGHT="27"></A></TD>
- <TD ALIGN="right"><IMG SRC="/images/search/contract/search2.gif" ALT="" WIDTH="13" HEIGHT="117" BORDER="0"></TD>
- </TR>
- <!-- End Search Elements -->
- <!-- Begin User Personalization (Must limit to 10 Characters)-->
- <TR>
- <TD COLSPAN="2"><TABLE><TR><TD COLSPAN="3" ALIGN="right"><IMG SRC="/images/home_con/welcom_1.gif" ALT="" WIDTH="156" HEIGHT="4" BORDER="0"></TD></TR>
- <TR><TD BGCOLOR="#333366"><IMG SRC="/images/home_con/welcom_2.gif" ALT="" WIDTH="17" HEIGHT="19" BORDER="0"></TD><TD BGCOLOR="#333366" VALIGN="middle"><NOBR><FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" COLOR="#99CC33" SIZE="-2">sopko</FONT></NOBR></TD><TD BGCOLOR="#333366" ALIGN="right"><A HREF="edit-user-form.pl?viewmode=contractuser"><IMG SRC="/images/home_con/welcom_3.gif" ALT="Edit" WIDTH="45" HEIGHT="19" BORDER="0"></A></TD></TR>
- </TABLE>
- </TD>
- </TR>
- <!-- End User Personalization -->
-
- <TR>
- <TD COLSPAN="2" ALIGN="right" VALIGN="top" WIDTH="157" BGCOLOR="#666699"><IMG BORDER="0" SRC="/images/ssolvecontents.gif" WIDTH="157" HEIGHT="37" ALT="Contents Of SunSolve"><BR>
-
-
-
-
-
- <!-- PILLS: CHANGE THE PILL FOR CURRENT SECTION TO THE HIGHLIGHTED PILL -->
- <!-- Beginning of Nav area -->
-<A HREF="show.pl?target=patches/patch-access" onmouseover="window.status='All Public Patches'; return true" onmouseout="window.status=''; return true">
-<IMG BORDER="0" SRC="/images/nav/p1.gif" WIDTH="157" HEIGHT="19" ALT="All Public Patches"></A><BR>
-<A HREF="suncourier.pl" onmouseover="window.status='Submit a Service Order'; return true" onmouseout="window.status=''; return true">
-<IMG BORDER="0" SRC="/images/nav/p5.gif" WIDTH="157" HEIGHT="19" ALT="Submit a Service Order"></A><BR>
-<A HREF="show.pl?target=resources/tools" onmouseover="window.status='Diagnostic Tools'; return true" onmouseout="window.status=''; return true">
-<IMG BORDER="0" SRC="/images/nav/p4.gif" WIDTH="157" HEIGHT="19" ALT="Diagnostic Tools"></A><BR>
-<A HREF="show.pl?target=help/collections" onmouseover="window.status='Support Docs.'; return true" onmouseout="window.status=''; return true">
-<IMG BORDER="0" SRC="/images/nav/cp2.gif" WIDTH="157" HEIGHT="19" ALT="Support Docs."></A><BR>
-<A HREF="show.pl?target=resources/y2k" onmouseover="window.status='Y2K Central'; return true" onmouseout="window.status=''; return true">
-<IMG BORDER="0" SRC="/images/nav/p3.gif" WIDTH="157" HEIGHT="19" ALT="Y2K Central"></A><BR>
-<A HREF="show.pl?target=security/sec" onmouseover="window.status='Security Information'; return true" onmouseout="window.status=''; return true">
-<IMG BORDER="0" SRC="/images/nav/p2.gif" WIDTH="157" HEIGHT="19" ALT="Security Information"></A><BR>
-<br><table width="157">
-<tr><td width="8">&nbsp;</td><td width="149">
-<table>
-<BR><tr><td><BR><img src="/images/line.gif" alt="------" width="140" height="11" border="0"><br>
- <A HREF="mark.pl"
- onmouseover="window.status='Marked Docs.';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Marked Docs.</FONT></A><BR>
- <A HREF="notify.pl"
- onmouseover="window.status='Notifications';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Notifications</FONT></A><BR>
- <A HREF="/plain-cgi/show.pl?target=home_con"
- onmouseover="window.status='Low Graphics';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Low Graphics</FONT></A><BR>
- <A HREF="show.pl?target=link"
- onmouseover="window.status='SunSolve Servers';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">SunSolve Servers</FONT></A><BR>
- <A HREF="show.pl?target=about_sunsolve"
- onmouseover="window.status='About SunSolve';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">About SunSolve</FONT></A><BR>
- <A HREF="feedback.pl"
- onmouseover="window.status='Contact Us';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Contact Us</FONT></A><BR>
- <A HREF="show.pl?target=help/sitemap"
- onmouseover="window.status='Site Map';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Site Map</FONT></A><BR>
- <A HREF="show.pl?target=article/article"
- onmouseover="window.status='Articles';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Articles</FONT></A><BR>
- <A HREF="show.pl?target=home_con"
- onmouseover="window.status='Home';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Home</FONT></A><BR>
- <A HREF="show.pl?target=help/faq"
- onmouseover="window.status='Help';return true"
- onmouseout="window.status='';return true">
- <font class="locallink" color="#dddddd">Help</FONT></A><BR>
-<br></td></tr></table></td></tr></table>
-<!-- End of Nav area -->
-
- </FORM>
- <br><br><!-- some spacers -->
- </TD>
- </TR>
- </TABLE>
- </TD>
- <TD VALIGN="TOP" WIDTH="466">
-
-
- <!--startindex-->
- <!-- ============ -->
- <!-- MAIN CONTENT -->
- <!-- ============ -->
-
-
-
-<table width=100%>
- <tr>
-<td width=100% valign=top>
-<CENTER><FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" SIZE="2">
-[&nbsp;<a href="retrieve.pl?type=0&doc=srdb%2F19195&display=plain">Printer Friendly Page</a>&nbsp;]
-[&nbsp;<b>Was this document useful? <a href="retrieve.pl?type=0&doc=srdb/19195&vote=yes">Yes</a> or <a href="retrieve.pl?type=0&doc=srdb/19195&vote=no">No</a></b>&nbsp;]<br>[&nbsp;<a href="notify.pl?action=add&doc=srdb%2F19195&type=synopsis">Notify if Document Changes</a>&nbsp;]
-[&nbsp;<a href="mark.pl?action=add&doc=srdb%2F19195&type=0">Mark Document for Download</a>&nbsp;]<br>[&nbsp;<a href="notify.pl">View/Edit Notifications</a>&nbsp;]
-[&nbsp;<a href="mark.pl">View/Edit Marked Documents</a>&nbsp;]<br></FONT></CENTER><br>
- <SCRIPT Language="JavaScript">
- <!-- Hide javascript from older browsers
- function jump()
- {
- var ctl = document.docform.jumplist;
- location.href = ctl.options[ctl.selectedIndex].value;
- }
- // End hiding contents -->
- </SCRIPT>
-<a name="top">
-<form name="docform"><div align=center><font size=2> Jump to <select name="jumplist" size=1 onchange="jump();"></font><option value="#Hardware">Hardware</option>
-<option value="#Product">Product</option>
-<option value="#Product-Area">Product Area</option>
-<option value="#Synopsis">Synopsis</option>
-<option value="#Problem-Description">Problem Description</option>
-<option value="#Document-Content">Document Content</option>
-<option value="#Problem-Solution">Problem Solution</option>
-<option value="#SRDB-ID">SRDB ID</option>
-<option value="#OS">OS</option>
-</select></div></form>
-<table width=100%>
-<tr bgcolor=#666699><td><font size=2 color=#ffffff><b>SRDB ID</b></font></td>
-<td bgcolor=#ffffff><font size=2>&nbsp;</font></td>
-<td><font size=2 color=#ffffff><b>Synopsis</b></font></td>
-<td bgcolor=#ffffff><font size=2>&nbsp;</font></td>
-<td><font size=2 color=#ffffff><b>Date</b></font></td>
-</tr>
-<tr bgcolor=#CCCCE7><td><font size=2><b>19195</b></font></td>
-<td bgcolor=#ffffff><font size=2>&nbsp;</font></td>
-<td><font size=2><b>Upgraded to 2.6, using xntpd, but the system clock is drifting. Worked fine</b></font></td>
-<td bgcolor=#ffffff><font size=2>&nbsp;</font></td>
-<td><font size=2><b>4 Sep 1999</b></font></td>
-</tr>
-</table><br clear>
-<table width=100%><tr bgcolor=#999999>
-<td><font size=2 color=#ffffff><b><a name=Problem-Description>Problem Description</a></b></font></td>
-<td align=right><b><a href="#top"><font size=2 color=#ffffff>Top</font></a></b></td></tr></table>
-<pre>Ever since upgrading to Solaris 2.6, the system clock has been drifting and
-there are messages like 'synchronisation lost', 'Previous time adjustment
-didn''t complete' and 'time reset (step)' a lot in the /var/adm/messages
-file. The system either was previously working fine with the freeware
-xntpd or the configuration was copied from another system that was
-using the freeware version.
--- 23-Apr-99 08:22 US/Eastern --</pre><table width=100%><tr bgcolor=#999999>
-<td><font size=2 color=#ffffff><b><a name=Problem-Solution>Problem Solution</a></b></font></td>
-<td align=right><b><a href="#top"><font size=2 color=#ffffff>Top</font></a></b></td></tr></table>
-<pre>The common lore for setting up xntpd on Solaris using
-the freeware version included the warning to set the
-kernel variable <font color=red>dosynctodr</font> to 0 in the /etc/system
-file thus: set <font color=red>dosynctodr</font>=0
-
-When using NTP on Solaris 2.6 or later, the kernel
-variable MUST be left at the default value of 1. Prior
-to 2.6 this variable controlled whether or not to rein
-in the softclock using the hardware clock, with the result
-that NTP and the hardware clock would fight for control of
-the soft clock; thus before 2.6 you had to set <font color=red>dosynctodr</font>
-to 0. At 2.6, every system call that adjusts the softclock
-also sets the hard clock, thus while NTP controls the soft
-clock, the hard clock is also controlled. Setting
-<font color=red>dosynctodr</font> to 0 reverts the behavior back to the pre 2.6
-defaulkt behavior, having exactly the opposite effect
-as that intended.
-
-Do not set <font color=red>dosynctodr</font> to 0.</pre><table width=100%>
-<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Product-Area>Product Area</a></b></font></td>
-<td bgcolor=#cccccc valign=top width=75%><font size=2>Bundled Network</font></td></tr>
-<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Product>Product</a></b></font></td>
-<td bgcolor=#cccccc valign=top width=75%><font size=2>NTP</font></td></tr>
-<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=OS>OS</a></b></font></td>
-<td bgcolor=#cccccc valign=top width=75%><font size=2>Solaris 2.6</font></td></tr>
-<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Hardware>Hardware</a></b></font></td>
-<td bgcolor=#cccccc valign=top width=75%><font size=2>Ultra 2</font></td></tr>
-<tr><td bgcolor=#999999 valign=top width=25%><font color=#ffffff size=2><b><a name=Document-Content>Document Content</a></b></font></td>
-<td bgcolor=#cccccc valign=top width=75%><font size=2>with freeware xntpd.</font></td></tr>
-</table><br clear>
-<font size=2><a href="#top">Top</a></font><br><br>
-</td></tr></table>
-
- <!-- =================== -->
- <!-- END OF MAIN CONTENT -->
- <!-- =================== -->
- <!--stopindex-->
-
- <!-- DON'T CHANGE INFORMATION OTHER THAN titlebar BELOW THIS LINE -->
-
- <!-- Altered Table Structure from Template to format properly with new design -->
- </TD>
- </TR>
- <TR>
- <TD>&nbsp;</TD>
- <TD VALIGN="top">
- <center>
- <IMG SRC="/images/cg_grey_line.gif" ALT="" WIDTH="466" HEIGHT="2" BORDER="0"><BR>
- <IMG SRC="/images/cg_clear.gif" ALT="" WIDTH="1" HEIGHT="2" BORDER="0" HSPACE="0" VSPACE="4">
- </center>
- <CENTER>
- <FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" SIZE="2">
- [ <A HREF="edit-user-form.pl?viewmode=contractuser">Edit Account</A> ]
- [ <A HREF="show.pl?target=patches/patch-access">Patches</A> ]
- [ <A HREF="suncourier.pl">Submit a Service Order</A> ]<br>
- [ <A HREF="show.pl?target=resources/tools">Diagnostic Tools</A> ]
- [ <A HREF="show.pl?target=help/collections">Support Docs.</A> ]
- [ <A HREF="show.pl?target=resources/y2k">Y2K Central</A> ]
- [ <A HREF="show.pl?target=security/sec">Security Information</A> ] <br>
- [ <A HREF="show.pl?target=link">SunSolve Servers </A> ]
- [ <A HREF="show.pl?target=about_sunsolve">About SunSolve</A> ]
- [ <A HREF="feedback.pl">Contact Us</A> ]
- [ <A HREF="show.pl?target=help/sitemap">Site Map</A> ]
- [ <A HREF="show.pl?target=article/article">Articles</A> ]
- [ <A HREF="show.pl?target=home_con">Home</A> ]
- [ <A HREF="show.pl?target=help/faq">Help</A> ]
- </FONT>
- </CENTER>
-
-<!-- MAPS -->
-<MAP NAME="lefttop">
-<AREA SHAPE="rect" HREF="http://www.sun.com/MySun/" ALT="My Sun" COORDS="89,0 149,32">
-<AREA SHAPE="rect" HREF="show.pl?target=home_con" ALT="Home" COORDS="0,0 42,32">
-<AREA SHAPE="rect" HREF="http://www.sun.com/sales/" ALT="Buy" COORDS="54,0 78,32">
-</MAP>
-
-
-<MAP NAME="topnav">
-<AREA SHAPE="rect" HREF="http://www.sun.com/java/" ALT="Java Technologies" COORDS="4,0,67,32">
-<AREA SHAPE="rect" HREF="http://www.sun.com/products-n-solutions/" ALT="Products and Solutions" COORDS="74,0,141,32">
-<AREA SHAPE="rect" HREF="http://www.sun.com/service/" ALT="Support, Education, and Consulting" COORDS="148,0,249,32">
-<AREA SHAPE="rect" HREF="http://www.sun.com/tech/" ALT="Technology and Research" COORDS="261,0,324,32">
-<AREA SHAPE="rect" HREF="http://www.sun.com/developers/developers.html" ALT="For Developers" COORDS="334,0,396,32">
-<AREA SHAPE="rect" HREF="http://www.sun.com/corporateoverview/" ALT="Corporate Information" COORDS="406,0,482,32">
-</MAP>
-
-<!-- INSERT titlebar HREFS BELOW -->
-<MAP NAME="titlebar">
-<!-- LINK TO SEC HOME Removed because no longer needed on this template -->
-<AREA SHAPE="rect" HREF="/visual/home/" ALT="SunSolve Online(tm)" COORDS="0,21,215,51"> <!-- LINK TO CURRENT PILL HOME -->
-</MAP>
-
-
-<!-- begin copyright notice -->
-
-<BR>
-<CENTER>
-<FONT FACE="Geneva, Helvetica, Arial, SunSans-Regular" COLOR="#999999" SIZE="2">
-<br>
-Copyright 1994-1999 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303 USA.
-<br>
-All rights reserved.
-<a href="http://www.sun.com/share/text/SMICopyright.html">Legal Terms</a>.
-<a href="http://www.sun.com/privacy/">Privacy Policy</a>.
-</font>
-</CENTER>
-
-<!-- end copyright notice -->
-
- </TD>
- </TR>
-</TABLE>
-
-</BODY>
-</HTML>
-
diff --git a/html/build/hints/solaris.html b/html/build/hints/solaris.html
deleted file mode 100644
index 9dc2ab15d038..000000000000
--- a/html/build/hints/solaris.html
+++ /dev/null
@@ -1,144 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Solaris hints and kinks</title><link href="scripts/style.css" type="text/css" rel="stylesheet">
-
-</HEAD>
-<BODY>
-Information on compiling and executing ntpd under Solaris.
-<BR>
-Last Updated: Sun Jun 21 01:32:18 EDT 1998,
-John Hawkinson,
-<! -- This is deliberately not a mailto -- > &lt;jhawk@MIT.EDU&gt;
-<P>
-If you're not running Solaris 2.5.1 or later, it is likely
-that you will have problems; upgrading would be a really good plan.
-<P>
-<H3>All Solaris versions</H3>
-<P>
- We have a report that says starting with Solaris 2.6 we should leave
- <I>dosynctodr</I> alone.
- <A HREF="solaris-dosynctodr.html">Here is the report</A>.
-<P>
-Proper operation of ntp under Solaris may require setting the kernel
-variable <I>dosynctodr</I> to zero (meaning "do not synchronize the clock
-to the hardware time-of-day clock"). This can be done with the
-tickadj utility:
-<BLOCKQUOTE><TT>
-tickadj -s
-</TT></BLOCKQUOTE>
-If you prefer, it can also be done with the native Solaris kernel debugger:
-<BLOCKQUOTE><TT>
-echo dosynctodr/W0 | adb -k -w /dev/ksyms /dev/mem
-</BLOCKQUOTE></TT>
-<P>
-Or, it can also be set by adding a line to /etc/system:
-<BLOCKQUOTE><TT>
-set dosynctodr = 0
-</BLOCKQUOTE></TT>
-<P>
-Instead of the <I>tick</I> kernel variable, which many operating
-systems use to control microseconds added to the system time every
-clock tick (c.f. <A HREF="../../notes.html#frequency_tolerance">Dealing
-with Frequency Tolerance Violations</A>), Solaris has the variables
-<I>nsec_per_tick</I> and <I>usec_per_tick</I>.
-<P>
-<I>nsec_per_tick</I> and <I>usec_per_tick</I> control the number of
-nanoseconds and microseconds, respectively, added to the system clock
-each clock interrupt. Enterprising souls may set these based on
-information collected by ntpd in the <CODE>/etc/ntp.drift</CODE> file
-to correct for individual hardware variations.
-<P>
-On UltraSPARC systems, <I>nsec_per_tick</I> and <I>usec_per_tick</I>
-are ignored in favor of the <I>cpu_tick_freq</I> variable, which
-should be automatically be determined by the PROM in an accurate
-fashion.
-<P>
-In general, the same ntp binaries should not be used across multiple
-operating system releases. There is enough variation in the core operating
-system support for timekeeping that a rebuild of ntpd for the idiosyncracies
-of your specific operating system version is advisable.
-<P>
-It is recommended that ntp be started via a script like <A
-HREF="solaris.xtra.S99ntpd">this one</A>, installed in
-<CODE>/etc/init.d/ntpd</CODE> with a symbol link from
-<CODE>/etc/rc2.d/S99ntpd</CODE>.
-
-<H3>Solaris 2.6</H3>
-<P>
-Solaris 2.6 adds support for kernel PLL timekeeping, but breaks this
-support in such a fashion that using it worse than not. This is <A
-HREF="solaris.xtra.4095849"> SUN Bug ID 4095849</A>, and it is not yet
-fixed as of June 1998.
-<P>
-<H3>Solaris 2.5 and 2.5.1</H3>
-<P>
-On UltraSPARC systems, calculation of <I>cpu_tick_freq</I> is broken
-such that values that are off by significant amounts may be used
-instead. This unfortunately means that ntpd may have severe problems
-keeping synchronization. This is <A HREF="solaris.xtra.4023118"> SUN Bug ID
-4023118</A>. Bryan Cantrill <! -- &lt;bmc@eng.sun.com&gt; --> of Sun
-posted <A HREF="solaris.xtra.patchfreq">patchfreq</A>, a workaround script,
-to comp.protocols.time.ntp in March of 1997.
-<P>
-<HR>
-<H2>OLD DATA</H2>
-<STRONG>I can't vouch for the accuracy the information below this
-rule. It may be significantly dated or incorrect.</STRONG>
-<P>
-<P>
-<H3>Solaris 2.2</H3>
-<P>
-Solaris 2.2 and later contain completely re-written clock code to
-provide high resolution microsecond timers. A benefit of the
-re-written clock code is that adjtime does not round off its
-adjustments, so ntp does not have to compensate for this
-rounding. Under Solaris 2.2 and later, ntp #define's
-<CODE>ADJTIME_IS_ACCURATE</CODE>, and does not look for the <I>tickadj</I>
-kernel variable.
-<P>
-<H3>Solaris 2.1</H3>
-(This originally written by William L. Jones &lt;jones@chpc.utexas.edu&gt;)
-<P>
-Solaris 2.1 contains fairly traditional clock code, with <I>tick</I>
-and <I>tickadj</I>.
-<P>
-Since settimeofday under Solaris 2.1 only sets the seconds part of timeval
-care must be used in starting xntpd. I suggest the following start
-up script:
-<BLOCKQUOTE><TT>
-tickadj -s -a 1000
-<BR>ntpdate -v server1 server2
-<BR>sleep 20
-<BR>ntpdate -v server1 server2
-<BR>sleep 20
-<BR>tickadj -a 200
-<BR>xntpd
-</TT></BLOCKQUOTE>
-
-The first tickadj turns of the time of day clock and sets the tick
-adjust value to 1 millisecond. This will insure that an adjtime value
-of at most 2 seconds will complete in 20 seconds.
-<P>
-The first ntpdate will set the time to within two seconds
-using settimeofday or it will adjust time using adjtime.
-<P>
-The first sleep insures the adjtime has completed for the first ntpdate.
-<P>
-The second ntpdate will use adjtime to set the time of day since the
-clock should be within 2 seconds of the correct time.
-<P>
-The second tickadj set the tick adjust system value to 5 microseconds.
-<P>
-The second sleeps insure that adjtime will complete before starting
-the next xntpd.
-<P>
-I tried running with a tickadj of 5 microseconds with out much success.
-200 microseconds seems to work well.
-<P>
-<HR>
-Prior versions of this file had major text contributed by:
-<MENU>
-<LI>Denny Gentry &lt;denny@eng.sun.com&gt;
-</MENU>
-<BODY>
-</HTML>
diff --git a/html/build/hints/solaris.xtra.4023118 b/html/build/hints/solaris.xtra.4023118
deleted file mode 100644
index 84c5d15214b2..000000000000
--- a/html/build/hints/solaris.xtra.4023118
+++ /dev/null
@@ -1,36 +0,0 @@
- Bug Id: 4023118
- Category: kernel
- Subcategory: other
- State: integrated
- Synopsis: sun4u doesn't keep accurate time
- Description:
-
-[ bmc, 12/20/96 ]
-
-The clock on a sun4u drifts unacceptably. On a typical 143 mHz Ultra,
-the clock took 1.0001350 seconds to count 1 second. While this may seem
-trivial, it adds up quickly. In this case, the TOD chip will have to
-pull the clock forward by 2 seconds every 4 hours and 7 minutes.
-This drift rate is so high, that the clock is close to being too broken
-for NTP to guarantee correctness (in order for NTP's mechanism to work,
-it must be assured that the local clock drifts no more than 20 ms in 64
-seconds; this particular 143 mHz Ultra will drift by nearly 9 ms in that
-period). This problem has been reproduced on virtually all sun4u
-classes.
-
-The fundamental problem lies in the kernel's perception of ticks per
-second. The PROM is responsible for determining this figure exactly,
-and the kernel extracts it into the variable cpu_tick_freq. On sun4u's,
-this number is disconcertingly round: 143000000, 167000000, 248000000,
-etc. Indeed, a simple experiment revealed that these numbers were
-quite far from the actual ticks per second. Typical was the 143 mHz
-Ultra which was discovered to tick around 142,980,806 (+/- 10) times
-per second.
-
- Work around:
-
- Integrated in releases: s297_27
- Duplicate of:
- Patch id:
- See also:
- Summary:
diff --git a/html/build/hints/solaris.xtra.4095849 b/html/build/hints/solaris.xtra.4095849
deleted file mode 100644
index 8d3ce8074cfd..000000000000
--- a/html/build/hints/solaris.xtra.4095849
+++ /dev/null
@@ -1,74 +0,0 @@
- Bug Id: 4095849
- Category: kernel
- Subcategory: syscall
- State: evaluated
- Synopsis: time_constant value >6 with PLL in use leads to integer divide
- zero trap panic
- Description:
-If the time_constant parameter is 7 or higher, and the phase-lock looping model
-is in use, the system will take a "integer divide zero trap" panic in
-the clock routine as soon as the time_offset becomes non-zero.
-
-time_constant defaults to 0. The only place it is set is in the ntp_adjtime
-system call, from the 'constant' element of the timex structure argument.
-
- Work around:
-Never set the constant element of the timex structure passed to ntp_adjtime to
-a value larger than 6.
-
-satish.mynam@Eng 1998-04-30
-1. Use Sun's version of NTP software instead of PD version. This problem
-is not seen with Sun's NTP version (which is mostly eqivalent to PD NTP 3.4
-plus some Sun's local functionality futures).
-
-2. Workaround for the public domain NTP version ONLY:
- =====================================================
-The workaround for public domain NTP version is to disable the
-KERNEL_PLL from the NTP code. This way ntp_Adjtime() system call is
-totally bypassed without sacrificing any of the functionality of the
-NTP. The only hit you might see is the way kernel precision timminig
-is done without the PLL algorithm in the kernel.
-
- The easiest way to disable ntp_adjtime option is(without changing
- any makefiles or other config files) to disable the KERNEL_PLL
- value in the ./config.h file.
-
-After doing a ./configure for probing for all the necessary tools(compilers,
-os version, libraries), please comment out KERNEL_PLL macro in
-the ./config.h file. This will disable the KERNEL_PLL part of the source
-code and the newly obtained xntpd is just similar to the old one but it
-does not use ntp_adjtime() system call. This prevents it from panic'ng
-the kernel.
-
-/*#define KERNEL_PLL 1*/
-
-I complied a new xntpd binary this way and it does nothave any ntp_adjtime()
-related stuff.
-
-Default:
-=======
-/net/divya/export/home/mynam/public_domain/ntp/xntp3-5.92/xntpd>strings
-xntpd |
-grep ntp_adjtime
-354:adj_frequency: ntp_adjtime failed: %m
-357:loop_config: ntp_adjtime() failed: %m
-435:get_kernel_info: ntp_adjtime() failed: %m
-
-With KERNEL_PLL disabled in config.h file
--=======================
-
-/net/divya/export/home/mynam/public_domain/ntp/xntp3-5.92/xntpd>strings
-xntpd.nopll | grep ntp_adjtime
-
- Integrated in releases:
- Duplicate of:
- Patch id:
- See also: 4133517
- Summary:
-If the time_constant parameter is 7 or higher, and the phase-lock looping model
-is in use, the system will take a "integer divide zero trap" panic in
-the clock routine as soon as the time_offset becomes non-zero.
-
-time_constant defaults to 0. The only place it is set is in the ntp_adjtime
-system call, from the 'constant' element of the timex structure argument.
-----------------------------------------------------------------------------
diff --git a/html/build/hints/solaris.xtra.S99ntpd b/html/build/hints/solaris.xtra.S99ntpd
deleted file mode 100644
index d8058fd43d42..000000000000
--- a/html/build/hints/solaris.xtra.S99ntpd
+++ /dev/null
@@ -1,21 +0,0 @@
-#!/bin/sh
-if [ $1 = "start" ]; then
- if [ -x /usr/local/bin/xntpd ]; then
- echo "Starting NTP daemon, takes about 1 minute... "
- # dosynctodr may need to be left alone as of with Solaris 2.6
- # The following line is unnecessary if you turn off
- # dosynctodr in /etc/system.
- /usr/local/bin/tickadj -s
- /usr/local/bin/ntpdate -v server1 server2
- sleep 5
- /usr/local/bin/xntpd
- fi
-else
- if [ $1 = "stop" ]; then
- pid=`/usr/bin/ps -e | /usr/bin/grep xntpd | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
- if [ "${pid}" != "" ]; then
- echo "Stopping Network Time Protocol daemon "
- /usr/bin/kill ${pid}
- fi
- fi
-fi
diff --git a/html/build/hints/solaris.xtra.patchfreq b/html/build/hints/solaris.xtra.patchfreq
deleted file mode 100644
index 9600881500e8..000000000000
--- a/html/build/hints/solaris.xtra.patchfreq
+++ /dev/null
@@ -1,85 +0,0 @@
-#!/bin/ksh
-
-#
-# File: patchfreq
-# Author: Bryan Cantrill (bmc@eng.sun.com), Solaris Performance
-# Modified: Sat Apr 26 04:00:59 PDT 1997
-#
-# This is a little script to patch a 5.5 or 5.5.1 kernel to get around
-# the cpu_tick_freq inaccuracy. Before running this script, one must
-# know the true frequency of one's CPU; this can be derived by NTP,
-# or by observing the clock relative to the time-of-day chip over a
-# long period of time (the TOD will pull system time when it drifts
-# by more than two seconds).
-#
-# Patching a kernel can render a machine unbootable; do not run this
-# script unless you are prepared to accept that possibility. It
-# is advisable to have a backout path (e.g. net booting, an alternate
-# boot disk, an installation CD) should your machine fail to boot.
-#
-# This is not a product of Sun Microsystems, and is provided "as is",
-# without warranty of any kind expressed or implied including, but not
-# limited to, the suitability of this script for any purpose.
-#
-
-if [ $# -eq 0 ]; then
- echo "Usage: $0 cpu_tick_freq [ alternate_kernel ]"
- exit 1
-fi
-
-cpu_tick_freq=$1
-kernel=/platform/sun4u/kernel/unix
-
-if [ $# -eq 2 ]; then
- kernel=$2
-fi
-
-if [ ! -w $kernel ]; then
- echo "$0: Cannot open $kernel for writing."
- exit 1
-fi
-
-arch=`echo utsname+404?s | adb $kernel | cut -d: -f2`
-
-if [ ! $arch = "sun4u" ]; then
- echo "Patch only applies to sun4u"
- exit 1
-fi
-
-rel=`echo utsname+202?s | adb $kernel | cut -d: -f2`
-
-if [ ! $rel = "5.5" ] && [ ! $rel = "5.5.1" ]; then
- echo "Patch only applies to 5.5 or 5.5.1..."
- exit 1
-fi
-
-nop="1000000" # nop
-store_mask="ffffe000" # mask out low 13 bits
-store="da256000" # st %o5, [%l5 + offset]
-
-instr=`echo setcpudelay+34?X | adb $kernel | cut -d: -f 2 | nawk '{ print $1 }'`
-
-if [ $instr = $nop ]; then
- echo "Instruction already patched..."
-else
- let masked="(16#$store_mask & 16#$instr) - 16#$store"
- if [ $masked -ne 0 ]; then
- echo "Couldn't find instruction to patch; aborting."
- exit 1
- fi
-
- if ! echo setcpudelay+34?W $nop | adb -w $kernel 1> /dev/null
- then
- echo "adb returned an unexpected error; aborting."
- fi
-fi
-
-echo "Patching cpu_tick_freq to $cpu_tick_freq..."
-
-if ! echo cpu_tick_freq?W 0t$cpu_tick_freq | adb -w $kernel 1> /dev/null; then
- echo "adb returned an unexpected error; aborting."
- exit 1
-fi
-
-echo "$kernel successfully patched."
-exit 0
diff --git a/html/build/hints/sun4 b/html/build/hints/sun4
deleted file mode 100644
index 424fa1873824..000000000000
--- a/html/build/hints/sun4
+++ /dev/null
@@ -1,15 +0,0 @@
-Notes on CPU clock oscillator tolerance with SunOS 4.1.1 and 4.1.3
-
-A bug in SunOS 4.1.1 results in the kernel time losing 1 microsecond
-per tick of the system clock. The bug was fixed (bugid 1094383) for
-SunOS 4.1.1 and corrected in SunOS 4.1.3. The easiest way to fix this
-is to replace the 4.1.1 binary clock.o with the corresponding 4.1.3
-binary. Without this change it is necessary to use the tickadj program
-included in this distribution with the -t 9999 option.
-
-The tickadj option will work in all cases except when the kernel has
-been modified to correct the CPU clock oscillator frequency using a
-1-pps signal from a precision source. The bugfix must be installed for
-this wrinkle to work properly.
-
-Dave Mills (mills@udel.edu)
diff --git a/html/build/hints/svr4-dell b/html/build/hints/svr4-dell
deleted file mode 100644
index 2c92f8a6337e..000000000000
--- a/html/build/hints/svr4-dell
+++ /dev/null
@@ -1,8 +0,0 @@
-Notes on the DELL SVR4.
-
-You should use -DSETTIMEOFDAY_BROKEN.
-
-Philip.Gladstone@mail.citicorp.com
-
-(XXX But there is no checking for SETTIMEOFDAY_BROKEN in the code)
-
diff --git a/html/build/hints/svr4_package b/html/build/hints/svr4_package
deleted file mode 100644
index b9f5ca391f34..000000000000
--- a/html/build/hints/svr4_package
+++ /dev/null
@@ -1,33 +0,0 @@
-Date: Wed, 12 Apr 1995 12:42:03 +0100
-Message-ID: <513.797686923@concurrent.co.uk>
-From: Andy Chittenden <asc@concurrent.co.uk>
-
-Dave
-
-Here is a uuencoded, compressed tar file. The only file I've
-changed is Makefile - I've included the full file rather than diffs.
-There are some new files as well:
-
- xntp shell script that starts up ntp during boot up
- (the packaging stuff creates links to it so it comes
- up at run level 2). As with all svr4 start/stop
- scripts, it takes one parameter which is either
- start or stop. It assumes that ntp.conf is in
- /etc/inet/ntp.conf (where it should be on svr4
- machines).
- prototype describes the file contents of the package.
- You might like to review its contents to
- see whether you want to include any other
- files or remove some. NB I've made the man
- pages go into 1m as they should on svr4.
- preinstall runs before installation takes place. It
- ensures that ntp is down if it is up before
- installing a replacement package
- postinstall starts up ntp after package installation.
- preremove brings down ntp before removing the package.
-
-You create a package using "make package". This creates a file
-called xntp.pkg. To install this package, you use
-"pkgadd -d `pwd`/xntp.pkg xntp". This will start up ntp if
-/etc/inet/ntp.conf exists. If you don't want the package anymore, use
-"pkgrm xntp". I have tested this on Solaris 2.4.
diff --git a/html/build/hints/todo b/html/build/hints/todo
deleted file mode 100644
index e0e5ffa37696..000000000000
--- a/html/build/hints/todo
+++ /dev/null
@@ -1,4 +0,0 @@
-Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>:
- Any change in a source file in the lib directory causes all files to
- be recompiled (because the objects are removed). Add a better rule for
- make to update the library. Maybe just remove "-rm -f $?".
diff --git a/html/build/hints/vxworks.html b/html/build/hints/vxworks.html
deleted file mode 100644
index 95ad22224890..000000000000
--- a/html/build/hints/vxworks.html
+++ /dev/null
@@ -1,82 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <title>vxWorks Port of NTP</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body link="#00008B" vlink="#8B0000">
- <h1>VxWorks port of NTP</h1>
- <p>Creating a port for vxWorks posed some problems. This port may help as a starting point for similar ports to real-time OS's and other embeddable kernels, particularly where main() is not allowed, and where the configure scripts need to be altered.</p>
- <h1><b>Configuration issues</b></h1>
- <p>I decided to do as little invasive surgery as possible on the NTP code, so I brought the vxWorks header tree in line with the standard unix tree. The following changes were needed, as a side effect these changes will allow for easy porting of other autoconfigure enabled code.</p>
- <p>Where I have 386 you will need to put in your target type. The vxWorks tree entry point is /usr/wind. If these are the same for your system, you should be able to cut and paste the changes.</p>
- <p><blink>WARNING: Check you are not overwriting files, before entering the following: there should be no conflict, but check first... </blink></p>
- <p>export CC=&quot;cc386 -nostdlib -m486 -DCPU=I80486 -I/usr/wind/target/h&quot;<br>
- export RANLIB=ranlib386<br>
- export AR=ar386<br>
- export VX_KERNEL=/usr/wind/target/config/ims_std_bsp/vxWorks<br>
- cd /usr/wind/target/sys<br>
- ln -s ../signal.h<br>
- ln -s ../time.h<br>
- ln -s socket.h sockio.h<br>
- ln -s ../selectLib.h select.h<br>
- ln -s ../timers.h<br>
- touch file.h param.h resource.h utsname.h var.h ../netdb.h ../a.out.h ../termios.h<br>
- echo &quot; ******ADD #include \&quot;sys/times.h\&quot; to sys/time.h &quot;</p>
- <p>The configure script must be changed in the following way to get the linking tests to work, once in the correct directory issue the following commands:<br>
- sed -e 's%main.*()%vxmain()%' configure &gt; configure.vxnew<br>
- mv configure.vxnew configure<br>
- chmod 755 configure</p>
- <p>The new version 4 of NTP requires some maths functions so it links in the maths library (-lm) in the ntpd <a href="../../ntpd/Makefile.am">Makefile.am</a> change the line &quot;ntpd_LDADD = $(LDADD) -lm&quot; by removing the &quot;-lm&quot;.<br>
- You are now ready to compile</p>
- <p><br>
- The <a href="../../configure.in">configure.in </a>file needed to be altered to allow for a host-target configuration to take place.</p>
- <ul>
- <li>The define SYS_VXWORKS was added to the compilation flags.
- <li>Little endianess is set if the target is of type iX86.
- <li>The size of char, integer, long values are all set. If Wind River ever changes these values they will need to be updated.
- <li>clock_settime() is defined to be used for setting the clock.
- <li>The Linking flags have -r added to allow for relinking into the vxWorks kernel
- </ul>
- <p>Unfortunately I have had to make use of the <a href="../../include/ntp_machine.h">ntp_machine.h </a>file to add in the checks that would have been checked at linking stage by autoconf, a better method should be devised.</p>
- <ul>
- <li>There is now a NO_MAIN_ALLOWED define that simulates command line args, this allows the use of the normal startup sysntax.
- <li>POSIX timers have been added.
- <li>Structures normally found in netdb.h have been added with, the corresponding code is in <a href="../../libntp/machines.c">machines.c </a>. Where possible the defines for these have been kept non-vxWorks specific.
- </ul>
- <p>Unfortunately there are still quite a few SYS_VXWORKS type defines in the source, but I have eliminated as many as possible. You have the choice of using the usrtime.a library avaliable from the vxworks archives or forgoing adjtime() and using the clock_[get|set]time().The <a href="../../include/ntp_machine.h">ntp_machine.h </a>file clearly marks how to do this.</p>
- <h1><b>Compilation issues</b></h1>
- <p>You will need autoconf and automake ... available free from the gnu archives worldwide.</p>
- <p>The variable arch is the target architecture (e.g. i486)</p>
- <p>mkdir A.vxworks (or whatever....)<br>
- cd A.vxworks<br>
- ../configure --target=arch-wrs-vxworks [any other options]<br>
- make</p>
- <p>Options I normally use are the --disable-all-clocks --enable-LOCAL-CLOCK flags. The program should proceed to compile without problem. The daemon ntpd, ntpdate, ntptrace, ntpdc, ntpq programs and of course the libraries are all fully ported. The other utilities are not, but they should be easy to port.</p>
- <h1>Running the software</h1>
- <p>Load in the various files, call them in the normal vxWorks function type manner. Here are some examples. Refer to the man pages for further information.</p>
- <p>ld &lt; ntpdate/ntpdate<br>
- ld &lt; ntpd/ntpd<br>
- ld &lt; ntptrace/ntptrace<br>
- ld &lt; ntpq/ntpq<br>
- ld &lt; ntpdc/ntpdc<br>
- ntpdate (&quot;-b&quot;, &quot;192.168.0.245&quot;)<br>
- sp(ntpd, &quot;-c&quot;, &quot;/export/home/casey/ntp/ntp.conf&quot;)<br>
- ntpdc(&quot;-c&quot;, &quot;monlist&quot;, &quot;192.168.0.244&quot;)<br>
- ntpq(&quot;-c&quot;, &quot;peers&quot;, &quot;192.168.0.244&quot;)<br>
- ntptrace(&quot;192.168.0.244&quot;)<br>
- </p>
- <h1>Bugs and such</h1>
- <p>Should you happen across any bugs, please let me know, or better yet fix them and submit a patch. Remember to make you patch general for Vxworks, not just for your particular architecture. <a href="http://www.ccii.co.za">CCII Systems (Pty) Ltd</a>, my ex employers, sponsored the time to this port. Please let me know how it goes, I would be most interested in offsets and configurations.</p>
- <p><br>
- </p>
- <p>Casey Crellin<br>
- <a href="mailto:casey@csc.co.za">casey@csc.co.za</a></p>
- <p><br>
- </p>
- </body>
-
-</html> \ No newline at end of file
diff --git a/html/build/hints/winnt.html b/html/build/hints/winnt.html
deleted file mode 100644
index 78de15d4e04c..000000000000
--- a/html/build/hints/winnt.html
+++ /dev/null
@@ -1,281 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>NTP on Windows NT</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h1>NTP 4.x for Windows NT</h1>
-
- <h2>Introduction</h2>
- The NTP 4 distribution runs as service on Windows NT 4.0, Windows 2000, Windows XP,
- Windows .NET Server 2003. It will NOT run on Windows 95, 98, ME, etc.
- The binaries work on multi-processor systems. This port has not been tested
- on the Alpha platform. This release now uses OpenSSL for authentication.
- IPv6 is not implemented yet for Win32 platforms.
- <h2>Authentication Keys</h2>
- With this release ntp-keygen is supported. See the <a href="../../keygen.html">
- ntp keygen documentation</a> for details on how to use ntp-keygen.
- <p>
- ntpd can now use the generated keys in the same way as on Unix platforms. Please
- refer to the <a href="../../authopt.html">Authentication Options</a> for details
- on how to use these.
- <p><B>NOTE:</B> ntpd and ntp-keygen both use OpenSSL which requires a random
- character file called .rnd by default. Both of these programs will automatically
- generate this file if they are not found. The programs will look for an
- environmental variable called RANDFILE and use that for the name of the
- random character file if the variable exists. If it does not exist it will look for an environmental
- variable called HOME and use that directory to search for a filed called .rnd
- in that directory. Finally, if neither RANDFILE nor HOME exists it will look
- in C:\ for a .rnd file. In each case it will search for and create the file
- if the environmental variable exists or in the C:\ directory if it doesn't.
- Note that ntpd normally runs as a service so that the only way that it will
- have either RANDFILE or HOME defined is if it is a System environmental
- variable or if the service is run under a specific account name and that
- account has one of those variables defined. Otherwise it will use the file
- "c:\.rnd". This was done so that OpenSSL will work normally on Win32 systems.
- This obviates the need to ship the OpenSSL.exe file and explain how to
- generate the .rnd file. A future version may change this behavior.
-
- <p>Refer to <a href="#Compiling">Compiling Requirements</a> and Instructions for how to compile the program.</p>
- <h2>Reference Clocks</h2>
- Reference clock support under Windows NT is tricky because the IO functions are
- so much different. Some of the clock types have been built into the ntpd executable
- and should work but have not been tested by the ntp project. If you have a clock
- that runs on Win32 and the driver is there but not implemented on Win32 you will have
- make the required configuration changes in config.h and then build ntpd from source
- and test it. The following reference clocks are known to work and are supported
- by Windows NT:
- <p><a href="../../driver1.html">Type 1</a> Undisciplined Local Clock (LOCAL)<br>
- <a href="../../driver29.html">Type 29</a> Trimble Navigation Palisade GPS (GPS_PALISADE)</p>
- <h2>Functions Supported</h2>
- All NTP functions are supported with some constraints. See the <a href="#ToDo">TODO list</a> below.
- Note that the ntptrace executable is not supported and you should use the PERL script
- version instead.
- <h2>Accuracy</h2>
- Greg Brackley has implemented a fantastic interpolation scheme that improves the precision of the NTP clock
- using a realtime thread (is that poetic or what!) which captures a tick count from the 8253 counter after each
- OS tick. The count is used to interpolate the time between operating system ticks.
- <p>On a typical 200+ MHz system NTP achieves a precision of about 5 microseconds and synchronizes the clock
- to +/-500 microseconds using the <a href="http://www.trimble.com/products/ntp">Trimble Palisade</a> as UTC reference.
- This allows distributed applications to use the 10 milliseconds ticks available to them with high confidence.</p>
- <h2>Binaries</h2>
- Recent InstallShield based executable versions of NTP for Windows NT (intel) are available from:
- <ul>
- <li><a href="http://www.trimble.com/oem/ntp">http://www.trimble.com/oem/ntp</a>
- <li><a href="http://www.five-ten-sg.com/">http://www.five-ten-sg.com/</a>
- <li><a href="http://www.meinberg.de/english/sw/ntp.htm">http://www.meinberg.de/english/sw/ntp.htm</a>
- </ul>
- <a name="ToDo"><h2>ToDo</h2></a>
- These tasks are in no particular order of priority.
- <ul>
- <li>Create a proper install/uninstall program
- <li>Add sntp to the list of supported programs
- <li>Add support for Visual C++ 7.0 or later (.NET)
- <li>Add IPv6 support
- <li>See if precision can be improved by using CPU cycle counter for tick interpolation.
- <li>Make precision time available to applications using NTP_GETTIME API
- </ul>
- <h2>Compiling Requirements</h2>
- <ul>
- <li>Windows NT 4.0 Windows 2000, Windows XP, or Windows.NET Server 2003
- <li>Microsoft Visual C++ 6.0. <B>NOTE:</B> VC++ 7.0 (aka .NET) is not yet supported
- but will probably work fine.
- <li>Some way of uncompressing and untarring the gzipped tar file.
- <li>OpenSSL must be built on the box before building NTP. Additional steps would
- be required to not use OpenSSL.
- </ul>
- <a name="Compiling"><h2>Compiling Instructions</h2></a>
- <ol>
- <li>Unpack and build OpenSSL according to the OpenSSL instructions for building on
- Windows. An environment variable named OPENSSL must be set up to specify the base path
- of the OpenSSL directory to be used to build the NTP package
- (e.g. <code>OPENSSL=C:\openssl-0.9.8b</code>).
- <li>Unpack the ntp-*.tar.gz archive using utilities such as WinZip.
- <li>Open the .\ports\winnt\ntp.dsw Visual C workspace
- <li>Batch build all projects
- <li>The built binaries can be found in the port\winnt\bin\Release subdirectory
- <li>In addition you will need to install the OpenSSL libeay32.dll
- <li>If you are shipping binaries in a kit it is strongly recommended that you
- ship this file (winnt.html) along with the binaries.
- </ol>
- <h2>Configuration File</h2>
- The default NTP configuration file path is %SystemRoot%<tt>\system32\drivers\etc\. </tt>(%SystemRoot%
- is an environmental variable that can be determined by typing &quot;set&quot; at the &quot;Command Prompt&quot;
- or from the &quot;System&quot; icon in the &quot;Control Panel&quot;).<br>
- Refer to your system environment and <tt>c</tt>reate your<tt> ntp.conf</tt> file in the directory
- corresponding to your system&nbsp; installation.<br>
- <tt>The older &lt;WINDIR&gt;\ntp.conf </tt>is still supported but you will get a log entry reporting that
- the first file wasn't found.
- <h2>Installation Instructions</h2>
- The <tt>instsrv</tt> program in the instsrv subdirectory of the distribution can be used to install 'ntpd' as
- a service and start automatically at boot time. Instsrv is automatically compiled with the rest of the distribution
- if you followed the steps above.
- <ol>
- <li>Start a command prompt and enter &quot;instsrv.exe &lt;pathname_for_ntpd.exe&gt;&quot;
- <li>Clicking on the &quot;Services&quot; icon in the &quot;Control Panel&quot; will display the list of
- currently installed services in a dialog box. The NetworkTimeProtocol service should show up in this list.
- Select it in the list and hit the &quot;Start&quot; button in the dialog box. The NTP service should start.
- <li>You can also stop and start the service by typing net start|stop NetworkTimeProtocol at the DOS prompt.
- <li>View the event log by clicking on the &quot;Event Viewer&quot; icon in the &quot;Administrative Tools&quot;
- group, there should be several successful startup messages from NTP. NTP will keep running and restart
- automatically when the machine is rebooted.
- </ol>
- You can change the start mode (automatic/manual) and other startup parameters corresponding to the NTP service
- in the &quot;Services&quot; dialog box if you wish.
- <h2>Removing NTP</h2>
- You can also use <tt>instsrv</tt> to delete the NTP service by entering: &quot;instsrv.exe remove&quot;
- <h2>Command Line Parameters and Registry Entries</h2>
- Unlike the Unix environment, there is no clean way to run 'ntpdate' and reset the clock before starting 'ntpd' at boot time.<br>
- NTP will step the clock up to 1000 seconds by default. While there is no reason that the system clock should be that much off
- during bootup if 'ntpd' was running before, you may wish to override this default and/or pass other command line directives.
- <p>Use the registry editor to edit the value for the ntpd executable under LocalMachine\System\CurrentControlSet\Services\NTP.</p>
- <p>Add the -g option to the ImagePath key, behind &quot;%INSTALLDIR&gt;\ntpd.exe&quot;. This will force NTP to accept
- large time errors (including 1.1.1980 00:00)</p>
- <h2>Bug Reports</h2>
- Send questions to <a href="news://comp.protocols.time.ntp">news://comp.protocols.time.ntp</a>
- and bug reports should be entered in <a href="http://bugzilla.ntp.org/">Bugzilla</a> on the
- NTP Web site.
- <h2>Change Log</h2>
- <h3>Last revision 2 July 2003&nbsp; Version 4.2.0</h3>
- <b>by Danny Mayer (mayer@ntp.org>)</b>
- <h3>Significant Changes:</h3>
- This latest release of NTP constitutes a major upgrade to its ability to build and
- run on Windows platforms and should now build and run cleanly. More importantly it
- is now able to support all authentication in the same way as Unix boxes. This does
- require the usage of OpenSSL which is now a prerequisite for build on Windows.
- ntp-keygen is now supported and builds on Win32 platforms.
-
- <h3>Last revision 16 February 1999&nbsp; Version 4.0.99e.</h3>
- <b>by Sven Dietrich (sven_dietrich@trimble.com)</b>
- <p><b>Significant Changes:</b></p>
- <ul>
- <li>Perl 5 is no longer needed to compile NTP. The configuration script which creates version.c
- with the current date and time was modified by Frederick Czajka [w2k@austin.rr.com] so that Perl
- is no longer required.
- </ul>
- <h3>Last revision 15 November 1999&nbsp; Version 4.0.98f.</h3>
- <b>by Sven Dietrich (sven_dietrich@trimble.com)</b>
- <p><b>Significant Changes:</b></p>
- <ul>
- <li>Fixed I/O problem delaying packet responses which resulted in no-replys to NTPQ and others.
- <li>The default configuration file path is <tt>&lt;WINDIR&gt;\system32\drivers\etc\ntp.conf.
- The old &lt;WINDIR&gt;\ntp.conf </tt>is still supported but you will get a log entry reporting
- that the first file wasn't found. The NTP 3.x legacy <tt>ntp.ini</tt> file is no longer supported.
- </ul>
- <b>Known Problems / TODO:</b>
- <ul>
- <li>MD5 and name resolution do not yet get along. If you define MD5, you cannot use DNS names, only IP numbers.
- </ul>
- <h3>Last revision 27 July 1999&nbsp; Version 4.0.95.</h3>
- This version compiles under WINNT with Visual C 6.0.
- <p>Greg Brackley and Sven Dietrich</p>
- <p>Significant changes:<br>
- -Visual Studio v6.0 support<br>
- -Winsock 2.0 support<br>
- -Use of I/O completion ports for sockets and comm port I/O<br>
- -Removed the use of multimedia timers (from ntpd, others need removing)<br>
- -Use of waitable timers (with user mode APC) and performance counters to fake getting a better time<br>
- -Trimble Palisade NTP Reference Clock support<br>
- -General cleanup, prototyping of functions<br>
- -Moved receiver buffer code to a separate module (removed unused members from the recvbuff struct)<br>
- -Moved io signal code to a separate module</p>
- <h3>Last revision:&nbsp; 20-Oct-1996</h3>
- This version corrects problems with building the XNTP<br>
- version 3.5-86 distribution under Windows NT.
- <p>The following files were modified:<br>
- &nbsp;blddbg.bat<br>
- &nbsp;bldrel.bat<br>
- &nbsp;include\ntp_machine.h<br>
- &nbsp;xntpd\ntp_unixclock.c<br>
- &nbsp;xntpd\ntp_refclock.c<br>
- &nbsp;scripts\wininstall\build.bat<br>
- &nbsp;scripts\wininstall\setup.rul<br>
- &nbsp;scripts\wininstall\readme.nt<br>
- &nbsp;scripts\wininstall\distrib\ntpog.wri<br>
- &nbsp;html\hints\winnt (this file)</p>
- <p>In order to build the entire Windows NT distribution you<br>
- need to modify the file scripts\wininstall\build.bat<br>
- with the installation directory of the InstallShield<br>
- software.&nbsp; Then, simply type &quot;bldrel&quot; for non-debug<br>
- or &quot;blddbg&quot; for debug executables.</p>
- <p>Greg Schueman<br>
- &nbsp;&nbsp;&nbsp; &lt;schueman@acm.org&gt;</p>
- <h3>Last revision:&nbsp; 07-May-1996</h3>
- This set of changes fixes all known bugs, and it includes<br>
- several major enhancements.
- <p>Many changes have been made both to the build environment as<br>
- well as the code.&nbsp; There is no longer an ntp.mak file, instead<br>
- there is a buildntall.bat file that will build the entire<br>
- release in one shot.&nbsp; The batch file requires Perl.&nbsp; Perl<br>
- is easily available from the NT Resource Kit or on the Net.</p>
- <p>The multiple interface support was adapted from Larry Kahn's<br>
- work on the BIND NT port.&nbsp; I have not been able to test it<br>
- adequately as I only have NT servers with one network<br>
- interfaces on which to test.</p>
- <p>Enhancements:<br>
- * Event Logging now works correctly.<br>
- * Version numbers now work (requires Perl during build)<br>
- * Support for multiple network interface cards (untested)<br>
- * NTP.CONF now default, but supports ntp.ini if not found<br>
- * Installation procedure automated.<br>
- * All paths now allow environment variables such as %windir%</p>
- <p>Bug fixes:<br>
- * INSTSRV replaced, works correctly<br>
- * Cleaned up many warnings<br>
- * Corrected use of an uninitialized variable in XNTPD<br>
- * Fixed ntpdate -b option<br>
- * Fixed ntpdate to accept names as well as IP addresses<br>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Winsock WSAStartup was called after a gethostbyname())<br>
- * Fixed problem with &quot;longjmp&quot; in xntpdc/ntpdc.c that<br>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; caused a software exception on doing a Control-C in xntpdc.<br>
- &nbsp;A Cntrl-C now terminates the program.</p>
- <p>See below for more detail:</p>
- <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Note: SIGINT is not supported for any Win32 application including<br>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Windows NT and Windows 95. When a CTRL+C interrupt occurs, Win32<br>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operating systems generate a new thread to specifically handle that<br>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interrupt. This can cause a single-thread application such as UNIX,<br>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to become multithreaded, resulting in unexpected behavior.<br>
- &nbsp;</p>
- <p>Possible enhancements and things left to do:<br>
- * Reference clock drivers for NT (at least Local Clock support)<br>
- * Control Panel Applet<br>
- * InstallShield based installation, like NT BIND has<br>
- * Integration with NT Performance Monitor<br>
- * SNMP integration<br>
- * Fully test multiple interface support<br>
- &nbsp;</p>
- <p>Known problems:<br>
- *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bug in ntptrace - if no Stratum 1 servers are available,<br>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; such as on an
- IntraNet, the application crashes.</p>
- <h3>Last revision:&nbsp; 12-Apr-1995</h3>
- This NTPv3 distribution includes a sample configuration file and the project<br>
- makefiles for WindowsNT 3.5 platform using Microsoft Visual C++ 2.0 compiler.<br>
- Also included is a small routine to install the NTP daemon as a &quot;service&quot;<br>
- on a WindowsNT box. Besides xntpd, the utilities that have been ported are<br>
- ntpdate and xntpdc. The port to WindowsNT 3.5 has been tested using a Bancomm<br>
- TimeServe2000 GPS receiver clock that acts as a strata 1 NTP server with no<br>
- authentication (it has not been tested with any refclock drivers compiled in).<br>
- Following are the known flaws in this port:<br>
- 1) currently, I do not know of a way in NT to get information about multiple<br>
- &nbsp;&nbsp; network interface cards. The current port uses just one socket bound to<br>
- &nbsp;&nbsp; INADDR_ANY address. Therefore when dealing with a multihomed NT time server,<br>
- &nbsp;&nbsp; clients should point to the default address on the server (otherwise the<br>
- &nbsp;&nbsp; reply is not guaranteed to come from the same interface to which the<br>
- &nbsp;&nbsp; request was sent). Working with Microsoft to get this resolved.<br>
- 2) There is some problem with &quot;longjmp&quot; in xntpdc/ntpdc.c that causes a<br>
- &nbsp;&nbsp; software exception on doing a Control-C in xntpdc. Be patient!<br>
- 3) The error messages logged by xntpd currently contain only the numerical<br>
- &nbsp;&nbsp; error code. Corresponding error message string has to be looked up in<br>
- &nbsp;&nbsp; &quot;Books Online&quot; on Visual C++ 2.0 under the topic &quot;Numerical List of Error<br>
- &nbsp;&nbsp; Codes&quot;.
- <p>Last HTML Update: November 17, 1999<br>
- <a href="mailto://sven_dietrich@trimble.com">Sven_Dietrich@Trimble.COM</a></p>
- </body>
-
-</html>
diff --git a/html/build/patches.html b/html/build/patches.html
deleted file mode 100644
index 00b2923351e0..000000000000
--- a/html/build/patches.html
+++ /dev/null
@@ -1,36 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <title>Patching Procedures</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h3>Patching Procedures</h3>
- <img src="../pic/alice38.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/%7emills/pictures.html"> rom <i>Alice's Adventures in Wonderland</i>, Lewis Carroll</a>
- <p>The Mad Hatter needs patches.</p>
- <p>Last update: <csobj format="ShortTime" h="25" locale="00000409" region="0" t="DateTime" w="99">12:56 AM</csobj> UTC <csobj format="LongDate" h="25" locale="00000409" region="0" t="DateTime" w="266">Saturday, March 20, 2004</csobj></p>
- <br clear="left">
- <hr>
- <p>A distribution so widely used as this one eventually develops numerous barnacles as the result of <a href="porting.html">porting</a> to new systems, idiosyncratic new features and just plain bugs. In order to help keep order and make maintenance bearable, we ask that proposed changes to the distribution be submitted in the following form.</p>
- <ol>
- <li>Please submit patches to <a href="mailto:bugs@mail.ntp.org">bugs@mail.ntp.org</a> in the form of either unified-diffs (<tt>diff -u</tt>) or context-diffs (<tt>diff -c</tt>).
- <li>Please include the <strong>output</strong> from <tt>config.guess</tt> in the description of your patch. If <tt>config.guess</tt> does not produce any output for your machine, please fix that, too!
- <li>Please base the patch on the root directory of the distribution. The preferred procedure here is to copy your patch to the root directory and mumble
- <p><tt>patch -p &lt;your_patch&gt;</tt></p>
- <li>Please avoid patching the RCS subdirectories; better yet, clean them out before submitting patches.
- <li>If you have whole new files, as well as patches, wrap the files and patches in a shell script. If you need to compress it, use either GNU <tt>gzip</tt> or the stock Unix <tt>compress</tt> utility.
- <li>Don't forget the documentation that may be affected by the patch. Send us patches for the <tt>./htm</tt> files as well.
- <li>We would be glad to include your name, electric address and descriptive phrase in the <a href="../copyright.html">Copyright</a> page, if you wish.
- </ol>
- <p>Prior to ntp3-5.83 (releases up to and including ntp3.5f) a complete patch history back to the dark ages was kept in the <tt>./patches</tt> directory, which might have been helpful to see if the same problem occurred in another port, etc. Patches were saved in that directory with file name in the form <tt>patch.<i>nnn</i></tt>, where <i>nnn</i> was approaching 200. All patches in that directory have been made; so, if yours was there, it was in the distribution.</p>
- <p>Since we have been getting multple patches for some bugs, plus many changes are implemented locally, no two maintainers here use the same tools, and since we're not using any bug-tracking software or even source code control, there is currently no tracking of specific changes.</p>
- <p>The best way to see what's changed between two distributions is to run a <tt>diff</tt> against them.</p>
- <p>Thanks for your contribution and happy chime.</p>
- <hr>
- <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
- </body>
-
-</html>
diff --git a/html/build/porting.html b/html/build/porting.html
deleted file mode 100644
index 976cc6670ce3..000000000000
--- a/html/build/porting.html
+++ /dev/null
@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <title>Porting Hints</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h3>Porting Hints</h3>
- <img src="../pic/wingdorothy.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/%7emills/pictures.html">from <i>The Wizard of Oz</i>, L. Frank Baum</a>
- <p>Porting Dorothy in Oz
- </p>
- <p>Last update: <csobj format="ShortTime" h="25" locale="00000409" region="0" t="DateTime" w="99">12:56 AM</csobj> UTC <csobj format="LongDate" h="25" locale="00000409" region="0" t="DateTime" w="266">Saturday, March 20, 2004</csobj></p>
- <br clear="left">
- <hr>
- <p>NOTE: The following procedures have been replaced by GNU <tt>automake</tt> and <tt>autoconfigure</tt>. This page is to be updated in the next release.</p>
- <p>Porting to a new machine or operating system ordinarily requires updating the <tt>./machines</tt> directory and the <tt>./compilers</tt> directories in order to define the build environment and autoconfigure means. You will probably have to modify the <tt>ntp_machines.h</tt> file and <tt>&quot;l_stdlib.h&quot;</tt> files as well. The two most famous trouble spots are the I/O code in <tt>./ntpd/ntp_io.c</tt> and the clock adjustment code in <tt>./ntpd/ntp_unixclock.c</tt>.</p>
- <p>These are the rules so that older bsd systems and the POSIX standard system can coexist together.</p>
- <ol>
- <li>If you use <tt>select</tt> then include <tt>&quot;ntp_select.h&quot;</tt>. <tt>select</tt> is not standard, since it is very system dependent as to where it is defined. The logic to include the right system dependent include file is in <tt>&quot;ntp_select.h&quot;</tt>.
- <li>Always use POSIX definition of strings. Include <tt>&quot;ntp_string.h&quot;</tt> instead of <tt>&lt;string.h&gt;</tt>.
- <li>Always include <tt>&quot;ntp_malloc.h&quot;</tt> if you use <tt>malloc</tt>.
- <li>Always include <tt>&quot;ntp_io.h&quot;</tt> instead of <tt>&lt;sys/file.h&gt;</tt> or <tt>&lt;fnctl.h&gt;</tt> to get <tt>O_*</tt> flags.
- <li>Always include <tt>&quot;ntp_if.h&quot;</tt> instead of <tt>&lt;net/if.h&gt;</tt>.
- <li>Always include <tt>&quot;ntp_stdlib.h&quot;</tt> instead of <tt>&lt;stdlib.h&gt;</tt>.
- <li>Define any special defines needed for a system in <tt>./include/ntp_machine.h</tt> based on system identifier. This file is included by the <tt>&quot;ntp_types.h&quot;</tt> file and should always be placed first after the <tt>&lt;&gt;</tt> defines.
- <li>Define any special library prototypes left over from the system library and include files in the <tt>&quot;l_stdlib.h&quot;</tt> file. This file is included by the <tt>&quot;ntp_stdlib.h&quot;</tt> file and should ordinarily be placed last in the includes list.
- <li>Don't define a include file by the same name as a system include file.
- </ol>
- <p><tt>&quot;l_stdlib.h&quot;</tt> can contain any extra definitions that are needed so that <tt>gcc</tt> will shut up. They should be controlled by a system identifier and there should be a separate section for each system. Really this will make it easier to maintain.</p>
- <p>See <tt>include/ntp_machines.h</tt> for the various compile time options.</p>
- <p>When you are satisfied the port works and that other ports are not adversely affected, please send <a href="patches.html">patches</a> for the system files you have changed, as well as any documentation that should be updated, including the advice herein.</p>
- <p>Good luck.</p>
- <hr>
- <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
- </body>
-
-</html> \ No newline at end of file
diff --git a/html/build/quick.html b/html/build/quick.html
deleted file mode 100644
index 1693b5d7a2fc..000000000000
--- a/html/build/quick.html
+++ /dev/null
@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html>
-
- <head>
- <meta name="generator" content="HTML Tidy, see www.w3.org">
- <title>Quick Start</title>
- <link href="scripts/style.css" type="text/css" rel="stylesheet">
- </head>
-
- <body>
- <h3>Quick Start</h3>
- <img src="../pic/panda.gif" alt="gif" align="left">FAX test image for SATNET (1979).
- <p>The baby panda was scanned at University College London and used as a FAX test image for a demonstration of the DARPA Atlantic SATNET Program and the first transatlantic Internet connection in 1978. The computing system used for that demonstration was called the <a href="http://www.eecis.udel.edu/%7emills/database/papers/fuzz.pdf">Fuzzball</a> . As it happened, this was also the first Internet multimedia presentation and the first to use NTP in regular operation. The image was widely copied and used for testing purpose throughout much of the 1980s.</p>
- <p>Last update: <csobj format="ShortTime" h="25" locale="00000409" region="0" t="DateTime" w="99">01:01 AM</csobj> UTC <csobj format="LongDate" h="25" locale="00000409" region="0" t="DateTime" w="266">Saturday, March 20, 2004</csobj></p>
- <br clear="left">
- <hr>
- <p>For the rank amateur the sheer volume of the documentation collection must be intimidating. However, it doesn't take much to fly the <tt>ntpd</tt> daemon with a simple configuration where a workstation needs to synchronize to some server elsewhere in the Internet. The first thing that needs to be done is to build the distribution for the particular workstation and install in the usual place. The <a href="build.html">Building and Installing the Distribution</a> page describes how to do this.</p>
- <p>While it is possible that certain configurations do not need a configuration file, most do require one. The file, called by default <tt>/etc/ntp.conf</tt>, need only contain one line specifying a remote server, for instance</p>
- <p><tt>server foo.bar.com</tt></p>
- <p>Choosing an appropriate remote server is somewhat of a black art, but a suboptimal choice is seldom a problem. There are about two dozen public time servers operated by National Institutes of Science and Technology (NIST), US Naval Observatory (USNO), Canadian Metrology Centre (CMC) and many others available on the Internet. Lists of public primary and secondary NTP servers maintained on the <a href="http://www.eecis.udel.edu/%7emills/ntp/servers.html">Public NTP TIme Servers</a> page, which is updated frequently.The lists are sorted by country and, in the case of the US, by state. Usually, the best choice is the nearest in geographical terms, but the terms of engagement specified in each list entry should be carefully respected.</p>
- <p>During operation <tt>ntpd</tt> measures and corrects for incidental clock frequency error and writes the current value to a file called by default <tt>/etc/ntp.drift</tt>. If <tt>ntpd</tt> is stopped and restarted, it initializes the frequency from this file. In this way the potentially lengthy interval to relearn the frequency error is avoided.</p>
- <p>That's all there is to it, unless some problem in network connectivity or local operating system configuration occurs. The most common problem is some firewall between the workstation and server. System administrators should understand NTP uses UDP port 123 as both the source and destination port and that NTP does not involve any operating system interaction other than to set the system clock. While almost all modern Unix systems have included NTP and UDP port 123 defined in the services file, this should be checked if <tt>ntpd</tt> fails to come up at all.</p>
- <p>The best way to confirm NTP is working is using the <a href="../ntpq.html"><tt>ntpq</tt></a> utility, although the <a href="../ntpdc.html"><tt>ntpdc</tt></a> utility may be useful in extreme cases. See the documentation pages for further information. In the most extreme cases the <tt>-d</tt> option on the <tt>ntpd</tt> command line results in a blow-by-blow trace of the daemon operations. While the trace output can be cryptic, to say the least, it gives a general idea of what the program is doing and, in particular, details the arriving and departing packets and detected errors, if present.</p>
- <p>Sometimes the <tt>ntpd</tt>. behavior may seem to violate the Principle of Least Astonishment, but there are good reasons for this. See the <a href="../ntpd.html">Network Time Protocol (NTP) daemon</a> page for revealing insights. See this page and its dependencies for additional configuration and control options. The <a href="../notes.html">Notes on Configuring NTP and Setting up a NTP Subnet</a> page contains an extended discussion of these options.</p>
- <hr>
- <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
- </body>
-
-</html> \ No newline at end of file
diff --git a/html/build/scripts/footer.txt b/html/build/scripts/footer.txt
deleted file mode 100644
index 89216ce97e12..000000000000
--- a/html/build/scripts/footer.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-document.write("\
-<table><tr>\
-<td width='50%' ><img src='../icons/home.gif' align='middle' alt='gif'>\
-<a href='../index.html'>Home Page</a></td>\
-<td width='50%' ><img src='../icons/mail2.gif' align='middle' alt='gif'>\
-<a href='http://www.ntp.org/contact.html'>Contacts</a></i></td>\
-</tr></table>") \ No newline at end of file
diff --git a/html/build/scripts/links10.txt b/html/build/scripts/links10.txt
deleted file mode 100644
index 7bf9d06e7e66..000000000000
--- a/html/build/scripts/links10.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-document.write("<ul>\
-<li class='inline'><a href='refclock.html'>Reference Clock Drivers</a><br>\
-<li class='inline'><a href='prefer.html'>Mitigation Rules and the <tt>prefer</tt> Keyword</a><br>\
-<li class='inline'><a href='howto.html'>How to Write a Reference Clock Driver</a><br>\
-</ul>") \ No newline at end of file
diff --git a/html/build/scripts/links11.txt b/html/build/scripts/links11.txt
deleted file mode 100644
index 1fce362a65d5..000000000000
--- a/html/build/scripts/links11.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-document.write("<ul>\
-<li class='inline'><a href='refclock.html'>Reference Clock Drivers</a><br>\
-<li class='inline'><a href='pps.html'>Pulse-per-second (PPS) Signal Interfacing</a><br>\
-<li class='inline'><a href='ldisc.html'>Line Disciplines and Streams Modules</a><br>\
-</ul>") \ No newline at end of file
diff --git a/html/build/scripts/links12.txt b/html/build/scripts/links12.txt
deleted file mode 100644
index 512cbcf4a83c..000000000000
--- a/html/build/scripts/links12.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-document.write("<ul>\
-<li class='inline'><a href='debug.html'>NTP Debugging Techniques</a><br>\
-<li class='inline'><a href='rdebug.html'>Debugging Reference Clock Drivers</a><br>\
-<li class='inline'><a href='msyslog.html'><tt>ntpd</tt> System Log Messages</a><br>\
-</ul>") \ No newline at end of file
diff --git a/html/build/scripts/links7.txt b/html/build/scripts/links7.txt
deleted file mode 100644
index 4a6f186a2fae..000000000000
--- a/html/build/scripts/links7.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-document.write("<ul>\
-<li class='inline'><a href='../confopt.html'>Server Options</a><br>\
-<li class='inline'><a href='../authopt.html'>Authentication Options</a><br>\
-<li class='inline'><a href='../monopt.html'>Monitoring Options</a><br>\
-</ul>") \ No newline at end of file
diff --git a/html/build/scripts/links8.txt b/html/build/scripts/links8.txt
deleted file mode 100644
index af33dca1cf77..000000000000
--- a/html/build/scripts/links8.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-document.write("<ul>\
-<li class='inline'><a href='refclock.html'>Reference Clock Drivers</a><br>\
-<li class='inline'><a href='drivers/driver7.html'>Radio CHU Audio Demodulator/Decoder</a><br>\
-<li class='inline'><a href='drivers/driver36.html'>Radio WWV/H Audio Demodulator/Decoder</a><br>\
-<li class='inline'><a href='drivers/driver6.html'>IRIG Audio Decoder</a>\
-</ul>") \ No newline at end of file
diff --git a/html/build/scripts/links9.txt b/html/build/scripts/links9.txt
deleted file mode 100644
index 38ffe90a7201..000000000000
--- a/html/build/scripts/links9.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-document.write("<ul>\
-<li class='inline'><a href='authopt.html'>Authentication Options</a><br>\
-<li class='inline'><a href='manyopt.html'>Automatic NTP Configuration Options</a><br>\
-<li class='inline'><a href='confopt.html'>Server Options</a><br>\
-<li class='inline'><a href='keygen.html'><tt>ntp-keygen</tt> - generate public and private keys</a>\
-<li class='inline'><a href='http://www.eecis.udel.edu/~mills/autokey.html'>Autonomous Authentication</a>\
-</ul>") \ No newline at end of file
diff --git a/html/build/scripts/style.css b/html/build/scripts/style.css
deleted file mode 100644
index 096b18a6a1d9..000000000000
--- a/html/build/scripts/style.css
+++ /dev/null
@@ -1,64 +0,0 @@
-body {background: #FDF1E1;
- color: #006600;
- font-family: "verdana", sans-serif;
- text-align: justify;
- margin-left: 5px;}
-
-p, h4, hr, li {margin-top: .6em; margin-bottom: .6em}
-li.inline {text-align: left; margin-top: 0; margin-bottom: 0}
-
-ul, dl, ol, {margin-top: .6em; margin-bottom: .6em; margin-left 5em}
-
-dt {margin-top: .6em}
-dd {margin-bottom: .6em}
-
-div.header {text-align: center;
- font-style: italic;}
-
-div.footer {text-align: center;
- font-size: 60%;}
-
-img.cell {align: left;}
-
-td.sidebar {width: 40px; align: center; valign: top;}
-img.sidebar {align: center; margin-top: 5px;}
-h4.sidebar {align: center;}
-
-p.top {background: #FDF1E1;
- color: #006600;
- position: absolute;
- margin-left: -90px;
- text-align: center;}
-
-a:link.sidebar {background: transparent;
- color: #990033;
- font-weight: bold;}
-
-a:visited.sidebar {background: transparent;
- color: #990033;
- font-weight: bold;}
-
-a:hover.sidebar {background: #FDF1E1;
- color: #006600;}
-
-img {margin: 5px;}
-
-div {text-align: center;}
-
-h1 {text-align: center;
- font-size: 250%;}
-
-caption {background: #EEEEEE;
- color: #339999;}
-
-tx {text-align: center;}
-
-th {background: #FFFFCC;
- color: #006600;
- text-align: center;
- text-decoration: underline;
- padding-top: 5px;}
-
-th.caption {background: #EEEEEE;
- color: #006600;
- text-align: center;} \ No newline at end of file