From owner-doc-jp@jp.freebsd.org  Sun Feb 13 04:08:13 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id EAA77050;
	Sun, 13 Feb 2000 04:08:13 +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 EAA77045
	for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 04:08:12 +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 EAA20936 for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 04:08:11 +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 EAA06279 for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 04:08:10 +0900 (JST)
Message-Id: <200002121908.EAA06279@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 DAA06737
	for <doc-jp@jp.freebsd.org>; Sun, 13 Feb 2000 03:31:29 +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:28 +0900
From: Hiroki Sato <hrs@geocities.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 62
Reply-To: doc-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+990727
X-Sequence: doc-jp 7022
Subject: [doc-jp 7022] books/handbook/advanced-networking/chapter.sgml #2
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

 $BB3$-$G$9!#(B

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

+        <sect4>
+          <title>Physical Server Requirements</title>
+            
+	  <para>There are several things to keep in mind when chosing a
+	    machine to use as a NIS server.  One of the unfortunate things
+	    about NIS is the level of dependency the clients have on the
+	    server.  If a client cannot contact the server for its NIS
+	    domain, very often the machine becomes unusable.  The lack of
+	    user and group information causes most systems to temporarily
+	    freeze up.  With this in mind you should make sure to choose a
+	    machine that won't be prone to being rebooted regularly, or
+	    one that might be used for development.  The NIS server should
+	    ideally be a stand alone machine whose sole purpose in life is
+	    to be an NIS server.  If you have a network that is not very
+	    heavily used, it is acceptable to put the NIS server on a
+	    machine running other services, just keep in mind that if the
+	    NIS server becomes unavailable, it will affect
+	    <emphasis>all</emphasis> of your NIS clients adversely.</para>
+        </sect4>
+      </sect3>
+
+      <sect3>
+        <title>NIS Servers</title>
+
+	<para> The canonical copies of all NIS information are stored on
+	  a single machine called the NIS master server.  The databases
+	  used to store the information are called NIS maps.  In FreeBSD,
+	  these maps are stored in
+	  <filename>/var/yp/[domainname]</filename> where
+	  <filename>[domainname]</filename> is the name of the NIS domain
+	  being served.  A single NIS server can support several domains
+	  at once, therefore it is possible to have several such
+	  directories, one for each supported domain.  Each domain will
+	  have its own independent set of maps.</para>
+
+	<para>NIS master and slave servers handle all NIS requests with
+	  the <command>ypserv</command> daemon.  <command>Ypserv</command>
+	  is responsible for receiving incoming requests from NIS clients,
+	  translating the requested domain and map name to a path to the
+	  corresponding database file and transmitting data from the
+	  database back to the client.</para>
+
+        <sect4>
+	  <title>Setting up a NIS master server</title>
+
+	  <para>Setting up a master NIS server can be relativly straight
+	    forward, depending on your needs.  FreeBSD comes with a handy
+	    script called <command>ypinit</command> that makes the initial
+	    setup procedure very easy.  A few steps are needed ahead of
+	    time to make the setup process go smoothly.</para>

--
| $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)
