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

PR: docs/147812

Browse source 
Improve wording in section "29.4.4.2.3 Setting up a NIS Slave Server" and make the paragraph about "automatic NIS map update on slave
server" easier to read/understand.

Original patch provided by:     Simon Wright (diver06 att gmx dott net)
This commit is contained in:
Johann Kois 2010-07-23 12:48:36 +00:00
parent bc5cd5cfff
commit c0f007d60a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=36094
1 changed files with 8 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

15
en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml
View file

@ -1709,13 +1709,14 @@ Don't forget to update map ypservers on ellington.</screen>
21 * * * * root /usr/libexec/ypxfr passwd.byuid</programlisting>
<para>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 is more important on busy networks where map
updates might not always complete.</para>
the maps on the master server. These entries are not
mandatory because the master server automatically attempts
to push any map changes to its slaves. However, due to the
importance of correct password information on other clients
depending on the slave server, it is recommended to
specifically force the password map updates frequently. This
is especially important on busy networks where map updates
might not always complete.</para>
<para>Now, run the command <command>/etc/netstart</command> on the
slave server as well, which again starts the NIS server.</para>