From c0f007d60ac86970a363ae45c1c7670755a584fb Mon Sep 17 00:00:00 2001 From: Johann Kois Date: Fri, 23 Jul 2010 12:48:36 +0000 Subject: [PATCH] PR: docs/147812 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) --- .../books/handbook/network-servers/chapter.sgml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml b/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml index 8619e2e4e9..1bd691793c 100644 --- a/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml @@ -1709,13 +1709,14 @@ Don't forget to update map ypservers on ellington. 21 * * * * root /usr/libexec/ypxfr passwd.byuid 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. + 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. Now, run the command /etc/netstart on the slave server as well, which again starts the NIS server.