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

[Giorgos Keramidas]

On 2006-02-21 16:40, Daniel Gerzo <danger at rulez.sk> wrote:
> I hope that this is fine now ;-)

> --- /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>

I think it is better to use either "mountd must be ..." or "The mountd
daemon must be...", but not what starts the newly added stuff above.

The order of the first sentence is slightly untasteful (the result
(having to restart mountd) precedes its cause (a change in the
/etc/exports file)).

The use of "it" is also a bit confusing.  Does "it" refer to mountd or
to the file?

Maybe we can use something like this?

+   <para>Every time a change is applied to the
+     <filename>/etc/exports</filename> file, the
+     <application>mountd</application> daemon must be forced to
+     recheck this file for changes.  This can be accomplished by
+     invoking the <command>mountd</command> &man.rc.8; script
+     with the appropriate parameter:</para>
+
+   <screen>&prompt.root; <userinput>/etc/rc.d/mountd reload</userinput></screen>
+
+   <para>Please refer to <xref linkend="configtuning-rcd"> for
+     more information about using <quote>rc scripts</quote>,
+     like <filename>/etc/rc.d/mountd</filename>.</para>