docs/93522: [patch] use rc.d script in example describing how to restart mountd in nework-servers chapter

[Daniel Gerzo]

The following reply was made to PR docs/93522; it has been noted by GNATS.

From: Daniel Gerzo <danger at rulez.sk>
To: bug-followup at FreeBSD.org, danger at rulez.sk
Cc:  
Subject: Re: docs/93522: [patch] use rc.d script in example describing how to restart mountd in nework-servers chapter
Date: Tue, 21 Feb 2006 17:32:13 +0100

 --n8g4imXOkfNTN/H1
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 Hello,
 
    I hope that this is fine now ;-)
 
 -- 
 Sincerely,
    Daniel Gerzo
 
 --n8g4imXOkfNTN/H1
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="rcd.diff"
 
 --- /usr/home/danger/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml.orig	Thu Feb 16 09:44:00 2006
 +++ /usr/home/danger/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml	Sat Feb 18 15:20:53 2006
 @@ -773,13 +773,16 @@
  /exports -alldirs -maproot=root      client01 client02
  /exports/obj -ro</programlisting>
  
 -      <para>You must restart
 -        <application>mountd</application> whenever you modify
 -        <filename>/etc/exports</filename> so the changes can take effect.
 -        This can be accomplished by sending the HUP signal
 -        to the <command>mountd</command> process:</para>
 +      <para>The <application>mountd</application> must be forced to
 +	recheck the <filename>/etc/exports</filename> file whenever it
 +	has been modified, so the changes can take effect.  This can be
 +	accomplished by invoking the <command>mountd</command>
 +	&man.rc.8; script with the appropriate parameter:</para>
  
 -      <screen>&prompt.root; <userinput>kill -HUP `cat /var/run/mountd.pid`</userinput></screen>
 +      <screen>&prompt.root; <userinput>/etc/rc.d/mountd reload</userinput></screen>
 +
 +      <para>Refer to <xref linkend="configtuning-rcd"> for more
 +	information about using rc scripts.</para>
  
        <para>Alternatively, a reboot will make FreeBSD set everything
          up properly.  A reboot is not necessary though.
 
 --n8g4imXOkfNTN/H1--