os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Correct assorted spelling and grammar errors.

Browse source 
PR:		27882
Submitted by:	Eric S. Van Gyzen <esv@vangyzen.net>
This commit is contained in:
Dima Dorfman 2001-06-05 01:37:15 +00:00
parent 362ff16a38
commit d15224bb59
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9541
2 changed files with 30 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

30
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.40 2001/05/11 09:25:31 murray Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.41 2001/05/28 13:41:56 sheldonh Exp $
-->
<chapter id="advanced-networking">
@ -1456,7 +1456,7 @@ ISDN BRI line</programlisting>
master's data files. NIS slave servers provide the redundancy,
which is needed in important environments. They also help
to balance the load of the master server: NIS Clients always
attach to the NIS server, whose response they get first, and
attach to the NIS server whose response they get first, and
this includes slave-server-replies.</para>
</listitem>
<listitem>
@ -1552,7 +1552,7 @@ ISDN BRI line</programlisting>
that it is part of. This is how multiple servers on one
network can tell which server should answer which request.
Think of the NIS domainname as the name for a group of hosts
that are related in someway way.</para>
that are related in some way.</para>
<para>Some organizations choose to use their Internet domainname
for their NIS domainname. This is not recommended as it can
@ -1641,7 +1641,7 @@ ISDN BRI line</programlisting>
</listitem>
</itemizedlist>
<para>Now, everything you have to do is to run the command
<para>Now, all you have to do is to run the command
<command>/etc/netstart</command> as superuser. It will
setup everything for you, using the values you defined in
<filename>/etc/rc.conf</filename>.</para>
@ -1815,8 +1815,8 @@ Don't forget to update map ypservers on ellington.</screen>
<para>These two lines force the slave to sync its maps with
the maps on the master server. Although this is
not mandatory, because the master server
tries to make sure any changes to it's NIS maps are
communicated to it's slaves, the password
tries to make sure any changes to its NIS maps are
communicated to its slaves, the password
information is so vital to systems that depend on the server,
that it is a good idea to force the updates. This is more
important on busy networks where map updates might not always
@ -1857,7 +1857,7 @@ Don't forget to update map ypservers on ellington.</screen>
<title>Setting up an NIS client</title>
<para>Setting up a FreeBSD machine to be a NIS client is fairly
straight forward.</para>
straightforward.</para>
<itemizedlist>
<listitem>
@ -2044,7 +2044,7 @@ basie&prompt.root;</screen>
users and/or machines. On larger networks, you
<emphasis>will</emphasis> forget to bar some users from logging
onto sensitive machines, or you may even have to modify each
machine separately, thus loosing the main benefit of NIS,
machine separately, thus losing the main benefit of NIS,
<emphasis>centralized</emphasis> administration.</para>
<para>The NIS developers' solution for this problem is called
@ -2122,7 +2122,7 @@ basie&prompt.root;</screen>
</row>
<row>
<!-- gluttony was omitted because it was too fat ;-) -->
<entry>pride, greed, envy, wraith, lust, sloth</entry>
<entry>pride, greed, envy, wrath, lust, sloth</entry>
<entry>Less important servers. All members of the IT
department are allowed to login onto these machines.</entry>
</row>
@ -2148,14 +2148,14 @@ basie&prompt.root;</screen>
-<replaceable>user</replaceable> line to each system's passwd
for each user who is not allowed to login onto that system.
If you forget just one entry, you could be in trouble. It may
feasible to do this correctly during the initial setup,
be feasible to do this correctly during the initial setup,
however you <emphasis>will</emphasis> eventually forget to add
the lines for new users during day-to-day operations. After
all, Murphy was an optimist.</para>
<para>Handling this situation with netgroups offers several
advantages. Each user need not be handled separately;
you assign a user to one or netgroup and allow or forbid
you assign a user to one or more netgroups and allow or forbid
logins for all members of the netgroup. If you add a new
machine, you will only have to define login restrictions for
netgroups. If a new user is added, you will only have to add
@ -2194,7 +2194,7 @@ INTERNS (,able,test-domain) (,baker,test-domain)</programlisting>
<para>The name of the host(s) where the following items are
valid. If you do not specify a hostname, the entry is
valid on all hosts. If you do specify a hostname, you
will a realm of darkness, horror and utter confusion.</para>
will enter a realm of darkness, horror and utter confusion.</para>
</listitem>
<listitem>
@ -2231,7 +2231,7 @@ INTERNS (,able,test-domain) (,baker,test-domain)</programlisting>
<programlisting>BIGGRP1 (,joe1,domain) (,joe2,domain) (,joe3,domain) [...]
BIGGRP2 (,joe16,domain) (,joe17,domain) [...]
BIGGRP3 (,joe32,domain) (,joe33,domain)
BIGGRP3 (,joe31,domain) (,joe32,domain)
BIGGROUP BIGGRP1 BIGGRP2 BIGGRP3</programlisting>
<para>You can repeat this process if you need more than 225
@ -2250,7 +2250,7 @@ ellington&prompt.root; <userinput>make</userinput>
<filename>netgroup</filename>,
<filename>netgroup.byhost</filename> and
<filename>netgroup.byuser</filename>. Use &man.ypcat.1; to
check if your new NIS map are available:</para>
check if your new NIS maps are available:</para>
<screen>
ellington&prompt.user; <userinput>ypcat -k netgroup</userinput>
@ -2944,7 +2944,7 @@ dhcp_flags=""</programlisting>
<sect3>
<title><filename>/etc/namedb/named.conf</filename></title>
<programlisting>// $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.40 2001/05/11 09:25:31 murray Exp $
<programlisting>// $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.41 2001/05/28 13:41:56 sheldonh Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy