old-www/LDP/nag/node157.html

49 lines
1.8 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>Taylor Configuration Files</TITLE>
</HEAD>
<BODY LANG="EN">
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
<B> Next:</B> <A HREF="node158.html">General Configuration Options-- the </A>
<B>Up:</B> <A HREF="node153.html">UUCP Configuration Files</A>
<B> Previous:</B> <A HREF="node156.html">Site Naming</A>
<BR> <P>
<H2><A NAME="SECTION0014340000">Taylor Configuration Files</A></H2>
<P>
We now return to the configuration files. Taylor UUCP gets its
information from the following files:
<P>
<P><P>
<P>
Taylor configuration files are generally made up of lines containing
keyword-value pairs. A hash sign introduces a comment that intends
to the end of the line. To use a hash sign by itself, you may escape it
with a backslash.
<P>
There are quite a number of options you can tune with these
configuration files. We can't go into all parameters here, but will
only cover the most important ones. They you should be able to
configure a modem-based UUCP link. Additional sections will describe
the modifications necessary if you want to use UUCP over TCP/IP or
over a direct serial line. A complete reference is given in the
Texinfo documents that accompany the Taylor UUCP sources.
<P>
<A NAME="5987"></A>
<A NAME="5988"></A>
<A NAME="5989"></A>
When you think you have configured your UUCP system completely, you
can check your configuration using the uuchk tool (located in
/usr/lib/uucp). uuchk reads your configuration files, and prints
out a detailed report of the configuration values used for each
system.
<P>
<BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>