2007-11-06 00:55:26

by Chuck Lever III

[permalink] [raw]
Subject: [PATCH 1/5] mount.nfs: Fix "statd not running" error message

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 <[email protected]>
---

utils/mount/nfsmount.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

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;


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs