From patchwork Wed Oct 24 15:25:58 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jeff Layton X-Patchwork-Id: 1639171 Return-Path: X-Original-To: patchwork-linux-nfs@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork2.kernel.org (Postfix) with ESMTP id 87695DFABE for ; Wed, 24 Oct 2012 15:26:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934933Ab2JXP0T (ORCPT ); Wed, 24 Oct 2012 11:26:19 -0400 Received: from mail-ye0-f174.google.com ([209.85.213.174]:41421 "EHLO mail-ye0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934931Ab2JXP0R (ORCPT ); Wed, 24 Oct 2012 11:26:17 -0400 Received: by mail-ye0-f174.google.com with SMTP id m12so88823yen.19 for ; Wed, 24 Oct 2012 08:26:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:cc:subject:date:message-id:x-mailer:in-reply-to :references:x-gm-message-state; bh=QmQQrFDsALqN6eLNJKCXHfWgniayA29K/EPZotYkpZQ=; b=QMdGh20XOwJPbgt/FzYpF03m0WQLSDSuoLaZOhGZwKYFY3XF6gXMEcOe2pIA+wkh3C WyU5FWvS3mmRPvZikf5GY2mK7W8XvZhvqJyIkJ0bcT1NfdTbEwHs8Suu+2FF05poYdNO IG6JsjlbDSPVtEhJ8NiZWArHdbCEh+7YnznVnFkP+d53GPiuFNQFCp0Ad6yAtceL5ZL+ K21MU2ornUWfuWQzfNer3Fk3B9TI/KEU5vIInttNtyP9tcOkSaxfN34FTTJaUHWKFXYA NDtWNOq5GSd94BfvLtDUHQOXFPYnVa5QSwkG0ghnjNnO3P6yv83+Lq9sAJBAJYHuAvW0 Jrzg== Received: by 10.58.137.229 with SMTP id ql5mr30038993veb.11.1351092377441; Wed, 24 Oct 2012 08:26:17 -0700 (PDT) Received: from salusa.poochiereds.net (cpe-107-015-110-129.nc.res.rr.com. [107.15.110.129]) by mx.google.com with ESMTPS id y15sm16388744vdt.9.2012.10.24.08.26.16 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 08:26:16 -0700 (PDT) From: Jeff Layton To: steved@redhat.com Cc: linux-nfs@vger.kernel.org Subject: [PATCH v2 09/10] nfsdcltrack: update the README about server startup order Date: Wed, 24 Oct 2012 11:25:58 -0400 Message-Id: <1351092359-25842-10-git-send-email-jlayton@redhat.com> X-Mailer: git-send-email 1.7.11.7 In-Reply-To: <1351092359-25842-1-git-send-email-jlayton@redhat.com> References: <1351092359-25842-1-git-send-email-jlayton@redhat.com> X-Gm-Message-State: ALoCoQlkg2XO1/AvCcj5OHl+JJwOlNCdWKFNePtRl/v1JdfuTU88ydt5dd8vBgTxkB9kPof5i/7i Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Now that nfsdcld is gone, remove the section about starting it up. Signed-off-by: Jeff Layton --- README | 23 ++--------------------- 1 file changed, 2 insertions(+), 21 deletions(-) diff --git a/README b/README index e55b2dd..61702f7 100644 --- a/README +++ b/README @@ -108,31 +108,12 @@ scripts can be written to work correctly. the lock. rpc.statd is only needed for NFSv2 and NFSv3 support. - 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 + E/ rpc.nfsd Starting nfsd will automatically start lockd. The nfs server will now be fully active and respond to any requests from clients. - G/ sm-notify + F/ 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