From: Harlan Stenn Date: Fri, 26 Mar 2004 02:13:54 +0000 (-0500) Subject: Documentation cleanup/resync with Dave. X-Git-Tag: NTP_4_2_3~174^2~6^2~2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0983a24923c3d572e905043646ca81dc2bc4c8e6;p=thirdparty%2Fntp.git Documentation cleanup/resync with Dave. bk: 406391e2D1fCRFhIRVix03pigNIfEA --- diff --git a/html/build/build.html b/html/build/build.html index 3e4ccd3596..0bb49afda3 100644 --- a/html/build/build.html +++ b/html/build/build.html @@ -10,7 +10,7 @@

Building and Installing the Distribution

- giffrom Pogo, Walt Kelly + giffrom Pogo, Walt Kelly

For putting out compiler fires.

Last update: 03:06 AM UTC Monday, October 13, 2003


@@ -40,29 +40,29 @@

Installation

As root, use the make install command to install the binaries in the destination directory. Most commonly, these programs are installed in /usr/local/bin, 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:

If the precision time kernel modifications are present, the following program is installed:

If the public key authentication functions are present, the following program is installed:

In some systems that include the capability to edit kernel variables, the following program is installed:

-

Cryptographic support, both symmetric and public key, requires one or more key files, commonly installed in /usr/local/etc. Public key cryptography requires a random seed file, usually called .rnd, installed in a dark place such as the root directory or /etc. Directions for generating keys is on the Authentication Options page.

+

Cryptographic support, both symmetric and public key, requires one or more key files, commonly installed in /usr/local/etc. Public key cryptography requires a random seed file, usually called .rnd, installed in a dark place such as the root directory or /etc. Directions for generating keys is on the Authentication Options page.

Configuration

-

You are now ready to configure the daemon and start it. You will need to create a NTP configuration file ntp.conf and a cryptographic key file ntp.keys. The latter file is necessary only for remote configuration support, if needed. Newbies should see the Quick Start page for orientation. Seasoned veterans can start with the ntpd - Network Time Protocol (NTP) daemon page and move on to the specific configuration option pages from there. A tutorial on NTP subnet design and configuration options is in the Notes on Configuring NTP and Setting up a NTP Subnet page.

+

You are now ready to configure the daemon and start it. You will need to create a NTP configuration file ntp.conf and a cryptographic key file ntp.keys. The latter file is necessary only for remote configuration support, if needed. Newbies should see the Quick Start page for orientation. Seasoned veterans can start with the ntpd - Network Time Protocol (NTP) daemon page and move on to the specific configuration option pages from there. A tutorial on NTP subnet design and configuration options is in the Notes on Configuring NTP and Setting up a NTP Subnet page.

If You Have Problems

-

If you have problems peculiar to the particular hardware and software environment (e.g. operating system-specific issues), browse the Hints and Kinks page. For other problems a tutorial on debugging technique is in the NTP Debugging Technique page. As always, the first line of general assistance is the NTP web site www.ntp.org 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 bugs@ntp.org. Bug reports of a specific nature on features implemented by the programmer corps mentioned in the Copyright page should be sent directly to the implementor listed in that page, with copy to bugs@ntp.org.

+

If you have problems peculiar to the particular hardware and software environment (e.g. operating system-specific issues), browse the Hints and Kinks page. For other problems a tutorial on debugging technique is in the NTP Debugging Technique page. As always, the first line of general assistance is the NTP web site www.ntp.org 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 bugs@ntp.org. Bug reports of a specific nature on features implemented by the programmer corps mentioned in the Copyright page should be sent directly to the implementor listed in that page, with copy to bugs@ntp.org.

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 config.guess in your bug report. It will look something like:

pdp11-dec-fuzzos3.4

Additional make commands

diff --git a/html/build/config.html b/html/build/config.html index 463214a28a..961779de66 100644 --- a/html/build/config.html +++ b/html/build/config.html @@ -10,9 +10,9 @@

Configuration Options

- giffrom Pogo, Walt Kelly + giffrom Pogo, Walt Kelly

Gnu autoconfigure tools are in the backpack.

-

Last update: 03:07 AM UTC Monday, October 13, 2003

+

Last update: 12:56 AM UTC Saturday, March 20, 2004


Table of Contents