Date: Sat, 12 Jun 2010 17:59:36 +0200 (CEST) From: Simon Wright <diver06@gmx.net> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/147812: Corrects English usage in NIS slave server setup in the Handbook (patch attached) Message-ID: <20100612155936.2CCBBD4C34@vmserver04.home.wright.org> Resent-Message-ID: <201006121620.o5CGK15X092552@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 147812 >Category: docs >Synopsis: Corrects English usage in NIS slave server setup in the Handbook (patch attached) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Sat Jun 12 16:20:01 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Simon Wright >Release: FreeBSD 7.3-RELEASE-p1 amd64 >Organization: >Environment: System: FreeBSD vmserver04.home.wright.org 7.3-RELEASE-p1 FreeBSD 7.3-RELEASE-p1 #3: Sun May 30 05:54:36 CEST 2010 root@vmserver04.home.wright.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Minor correction to the English usage in the NIS slave server setup paragraph relating to the reason for adding crontab entries to a slave. >How-To-Repeat: Visit the Handbook, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-nis.html >Fix: Doc update, patch attached. --- network-nis-old.html 2010-06-12 17:22:58.000000000 +0200 +++ network-nis.html 2010-06-12 17:43:41.000000000 +0200 @@ -40,7 +40,7 @@ <i class="AUTHORGROUP"><span class="CONTRIB">Written by</span> Bill Swingle.</i> <i class="AUTHORGROUP"><span class="CONTRIB">Enhanced by</span> Eric Ogren and Udo -Erdelhoff.</i> +Erdelhoff.</i> <div class="SECT2"> <h2 class="SECT2"><a id="AEN37266" name="AEN37266">29.4.1 What Is It?</a></h2> @@ -552,9 +552,9 @@ </pre> <p>These two lines force the slave to sync its maps with the maps on the master server. -Although these entries are not mandatory, since the master server attempts to ensure any -changes to its NIS maps are communicated to its slaves and because password information -is vital to systems depending on the server, it is a good idea to force the updates. This +Although these entries are not mandatory since the master server attempts to ensure any +changes to its NIS maps are communicated to its slaves, because password information +is vital to systems depending on the server it is a good idea to force the updates. This is more important on busy networks where map updates might not always complete.</p> <p>Now, run the command <tt class="COMMAND">/etc/netstart</tt> on the slave server as @@ -787,7 +787,7 @@ <h2 class="SECT2"><a id="NETWORK-NETGROUPS" name="NETWORK-NETGROUPS">29.4.7 Using Netgroups</a></h2> -<i class="AUTHORGROUP"><span class="CONTRIB">Contributed by</span> Udo Erdelhoff.</i> +<i class="AUTHORGROUP"><span class="CONTRIB">Contributed by</span> Udo Erdelhoff.</i> <p>The method shown in the previous section works reasonably well if you need special rules for a very small number of users and/or machines. On larger networks, you <span >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100612155936.2CCBBD4C34>