From cd9d242a13b719452d2f922e926454ae55998ca1 Mon Sep 17 00:00:00 2001
From: Remko Lodder <remko@FreeBSD.org>
Date: Fri, 13 Oct 2006 14:11:00 +0000
Subject: [PATCH] Add documentation about NFSlocking.

PR:			docs/103956
Submitted by:		novel
Facilitated by:		Snow B.V.
---
 .../handbook/network-servers/chapter.sgml     | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)

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 8fa9083f7d..d4625a88d4 100644
--- a/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml
@@ -821,6 +821,32 @@ mountd_flags="-r"</programlisting>
         options.</para>
     </sect2>
 
+    <sect2>
+      <title>Locking</title>
+
+      <para>Some applications (e.g. <application>mutt</application>)
+	require file locking to operate correctly.  In the case of
+	<acronym>NFS</acronym>, <application>rpc.lockd</application>
+	can be used for file locking.  To enable it, add the following
+	to the <filename>/etc/rc.conf</filename> file on both client
+	and server (it is assumed that the <acronym>NFS</acronym>
+	client and server are configured already):</para>
+
+      <programlisting>rpc_lockd_enable="YES"
+rpc_statd_enable="YES"</programlisting>
+
+      <para>Start the application by using:</para>
+
+      <screen>&prompt.root; <userinput>/etc/rc.d/nfslocking start</userinput></screen>
+
+      <para>If real locking between the <acronym>NFS</acronym> clients
+	and <acronym>NFS</acronym> server is not required, it is
+	possible to let the <acronym>NFS</acronym>client do locking
+	locally by passing <option>-L</option> to &man.mount.nfs.8;.
+	Refer to the &man.mount.nfs.8; manual page for further details.
+      </para>
+    </sect2>
+
     <sect2>
       <title>Practical Uses</title>