From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:25199 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753640Ab1LUUf1 (ORCPT ); Wed, 21 Dec 2011 15:35:27 -0500 From: Jeff Layton To: bfields@fieldses.org, steved@redhat.com Cc: linux-nfs@vger.kernel.org Subject: [PATCH v3 10/10] nfsdcld: update the README Date: Wed, 21 Dec 2011 15:35:22 -0500 Message-Id: <1324499722-10363-11-git-send-email-jlayton@redhat.com> In-Reply-To: <1324499722-10363-1-git-send-email-jlayton@redhat.com> References: <1324499722-10363-1-git-send-email-jlayton@redhat.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: Add info to the README about when this daemon should be started, and its build and runtime requirements. Signed-off-by: Jeff Layton --- README | 25 +++++++++++++++++++++++-- 1 files changed, 23 insertions(+), 2 deletions(-) diff --git a/README b/README index e7588cf..cb1d2f5 100644 --- a/README +++ b/README @@ -15,6 +15,8 @@ libraries. They are available from http://www.citi.umich.edu/projects/nfsv4/linux/libnfsidmap/ Otherwise use --disable-nfsv4 +To use the nfsdcld tracking daemon, nfsv4 support must be enabled, +and the libsqlite3 development libraries must be installed. 1. COMPILING @@ -106,12 +108,31 @@ scripts can be written to work correctly. the lock. rpc.statd is only needed for NFSv2 and NFSv3 support. - E/ rpc.nfsd + E/ nfsdcld + This daemon is only needed on kernels that support the nfsdcld + upcall, and only if the legacy client ID tracking isn't used. It + is also not needed if the server does not support NFSv4. + + To determine whether you need this or not, do the following: + + # cat /proc/fs/nfsd/versions + + That should yield a list of NFS versions that this kernel supports, + if "4" or later is not in that list, or they are prefixed with a "-" + then you don't need to run this daemon. Next: + + # cat /proc/fs/nfsd/nfsv4recoverydir + + If that file is not present, or the directory that the above command + outputs is not present, then this daemon is required in order to + support lock recovery by the clients when the server reboots. + + F/ rpc.nfsd Starting nfsd will automatically start lockd. The nfs server will now be fully active and respond to any requests from clients. - F/ sm-notify + G/ sm-notify This will notify any client which might have locks from before a reboot to try to reclaim their locks. This should start immediately after rpc.nfsd is started so that clients have a -- 1.7.1