[PATCH 6/6] nfsdcltrack: update the README about server startup order

[Jeff Layton <jlayton@redhat.com>]

If we eventually deprecate nfsdcld, then we can just remove this
section I think.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
 README | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/README b/README
index e55b2dd..f997783 100644
--- a/README
+++ b/README
@@ -110,8 +110,9 @@ scripts can be written to work correctly.
 
    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.
+       upcall, and only if the legacy client ID tracking and nfsdcltrack
+       aren'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:
 
@@ -124,7 +125,12 @@ scripts can be written to work correctly.
            # 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
+       outputs is not present, then check this:
+
+	   # modinfo nfsd | grep cltrack_prog
+
+       to see whether the kernel supports the nfsdcltrack upcall. If
+       none of those are configured then this daemon is required in order to
        support lock recovery by the clients when the server reboots.
 
    F/ rpc.nfsd
-- 
1.7.11.4