home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
x
/
xntp3.zip
/
README
< prev
next >
Wrap
Text File
|
1992-07-07
|
3KB
|
64 lines
This first set of instructions will allow you to make xntp version 3
for a single architecture; to set up separate compilation trees for
different architectures, see at end.
------- these instructions originally from Dennis Ferguson, ----------
------- University of Toronto <dennis@gw.ccie.utoronto.ca> -----------
To make this:
(1) Edit the Config file in this directory to match the machine you
are installing this on. You must at least make sure you configure
the correct byte order for the machine and indicate whether your
compiler understands `signed char' declarations or not. There are
other considerations as well.
(2) Type `make makefiles' to distribute the configuration info to the
Makefiles in the subdirectories.
(3) Type `make' to compile everything of general interest.
(4) Run the command `authstuff/authcert < authstuff/certdata'. If the
last word in each line isn't `OK' there is something wrong. Likely
you got the byte order wrong in the Config file. You will have to
recompile from scratch if you did.
(5) Type `make install' to put the binaries in the system directory
you mentioned in Config. At the time of writing this includes
the programs xntpd (the daemon), xntpdc (an xntpd-dependent query
program), ntpq (a standard query program), ntpdate (an rdate
replacement for boot time date setting and sloppy time keeping)
and xntpres (a program which provides name resolver support for
xntpd configuration).
(6) You are now ready to configure the daemon and start it. At this
point it might be useful to format and print the file doc/notes.me
and read a little bit. The sections on configuration and on
tickadj will be immediately useful.
All bug reports gratefully received.
Dennis
----------------------------------------------------------------------
If you want to hack on this code in a multi-architecture environment,
you can set up as follows:
(1) From this directory, run the mklinks script once for each
architecture. If this directory is /some/path/src,
./mklinks ../sun4 ../src
will create a tree under /some/path/sun4 with symbolic links to
all the source files.
(2) For each of the new directories, create or copy a Config file and
proceed as above.
(3) Now, when you install a bug fix, you can just re-make in each
directory (as long as no extra files appear, at least).
Since most of Dennis' bugs are probably overlaid by mine and others',
bug reports should go to me or the mailing list (ntp@ni.umd.edu).
Lars Mathiesen (University of Copenhagen) <thorinn@diku.dk>