From owner-doc-jp@jp.freebsd.org  Sun Feb 13 04:08:16 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id EAA77164;
	Sun, 13 Feb 2000 04:08:16 +0900 (JST)
	(envelope-from owner-doc-jp@jp.FreeBSD.org)
Received: from sv01.geocities.co.jp (sv01.geocities.co.jp [210.153.89.155])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id EAA77159
	for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 04:08:15 +0900 (JST)
	(envelope-from hrs@geocities.co.jp)
Received: from mail.geocities.co.jp (mail.geocities.co.jp [210.153.89.137]) by sv01.geocities.co.jp (8.9.3+3.2W/3.7W) with ESMTP id EAA20960 for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 04:08:15 +0900 (JST)
Received: from mail.hrs.jp (sutnmax1-ppp41.ed.noda.sut.ac.jp [133.31.173.51]) by mail.geocities.co.jp (1.3G-GeocitiesJ-3.3) with ESMTP id EAA06342 for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 04:08:13 +0900 (JST)
Message-Id: <200002121908.EAA06342@mail.geocities.co.jp>
Received: from localhost (alph.hrs.jp [192.168.0.10])
	by mail.hrs.jp (8.9.3/3.7W/DomainMaster) with ESMTP id DAA06735
	for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 03:31:18 +0900 (JST)
	(envelope-from hrs@hrs.jp)
To: doc-jp@jp.freebsd.org
X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Date: Sun, 13 Feb 2000 03:31:17 +0900
From: Hiroki Sato <hrs@geocities.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 78
Reply-To: doc-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+990727
X-Sequence: doc-jp 7024
Subject: [doc-jp 7024] books/handbook/advanced-networking/chapter.sgml #1
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org
X-Originator: hrs@geocities.co.jp

$B:4F#!wEl5~M}2JBg3X$G$9!#(B

 NIS $B4XO"$,DI2C$5$l$?(B advanced-networking/chapter.sgml $B$G$9!#(B
 $BNL$,B?$$$N$G!"$A$g$C$HJ,$1J}$,Bg$-$a$K$J$C$F$^$9!#(B

(books/handbook/advanced-networking/chapter.sgml 1.17 -> 1.18 #1)

+  <sect1 id="nis">
+    <title>NIS/YP</title>
+
+    <para><emphasis>Written by &a.unfurl;, 21 January 2000.</emphasis></para>
+
+    <sect2>
+      <title>What is it?</title>
+  
+      <para> NIS is an RPC-based client/server system that allows a group
+	of machines within an NIS domain to share a common set of
+	configuration files.  This permits a system administrator to set
+	up NIS client systems with only minimal configuration data and
+	add, remove or modify configuration data from a single
+	location.</para>
+    </sect2>
+  
+    <sect2>
+      <title>How does it work?</title>
+        
+      <para>There are 3 types of hosts in an NIS enviornment; master
+	servers, slave servers, and clients.  Servers act as a central
+	repository for host configuration information.  Master servers
+	hold the authoritatve copy of this information, while slave
+	servers mirror this information for redundancy.  Clients rely on
+	the servers to provide this information to them.</para>
+
+      <para>Information in many files can be shared in this manner.  The
+	<filename>master.passwd</filename>, <filename>group</filename>,
+	and <filename>hosts</filename> files are commonly shared via NIS.
+	Whenever a process on a client needs information that would
+	normally be found in these files locally, it makes a query to the
+	server it is bound to, to get this information.</para>
+    </sect2>
+    
+    <sect2>
+      <title>Using NIS/YP</title>
+  
+      <sect3>
+        <title>Planning</title>
+  
+        <para>If you are setting up a NIS scheme for the first time, it
+	  is a good idea to think through how you want to go about it.  No
+	  matter what the size of your network, there are a few decisions
+	  that need to be made.</para>
+  
+        <sect4>
+          <title>Choosing a NIS Domain Name</title>
+  
+          <para>This might not be the &ldquo;domainname&rdquo; that you
+	    are used to.  It is more accurately called the
+	    &ldquo;NIS domainname&rdquo;.  When a client broadcasts its
+	    requests for info, it includes the name of the NIS domain
+	    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>
+  
+	  <para>Some organizations choose to use their Internet domainname
+	    for their NIS domainname. This is not recommended as it can
+	    cause confusion when trying to debug network problems.  The
+	    NIS domainname should be unique within your network and it is
+	    helpful if it describes the group of machines it represents.
+	    For example, the Art department at Acme Inc. might be in the
+	    "acme-art" NIS domain.</para>
+        </sect4>

--
| $B:4F#(B $B9-@8!wEl5~M}2JBg3X(B <hrs@geocities.co.jp>
|
|                                  j7397067@ed.noda.sut.ac.jp(univ)
|                        hrs@jp.FreeBSD.org(FreeBSD doc-jp Project)
