From: Steve Dickson <steved@redhat.com>
Date: Wed, 16 Jan 2008 16:48:23 +0000 (-0500)
Subject: When mount.nfs reports that statd isn't running, it suggests using the "-o
X-Git-Tag: nfs-utils-1-1-2~25
X-Git-Url: https://git.decadent.org.uk/gitweb/?a=commitdiff_plain;h=0f3172012919d36e2a7e5bf46c388f8c028fc93e;p=nfs-utils.git

When mount.nfs reports that statd isn't running, it suggests using the "-o
nolocks" option, which doesn't exist.  It should say "-o nolock".

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
---

diff --git a/utils/mount/nfsmount.c b/utils/mount/nfsmount.c
index 23dd2f6..3d2ebb1 100644
--- a/utils/mount/nfsmount.c
+++ b/utils/mount/nfsmount.c
@@ -848,7 +848,7 @@ noauth_flavors:
 		if (!start_statd()) {
 			nfs_error(_("%s: rpc.statd is not running but is "
 				"required for remote locking.\n"
-				"   Either use '-o nolocks' to keep "
+				"   Either use '-o nolock' to keep "
 				"locks local, or start statd."),
 					progname);
 			goto fail;