From: NeilBrown <neilb@suse.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH nfs-utils 0/2] Fix problems caused by rpc.statd being unresponsive.
Date: Thu, 17 Dec 2015 15:27:34 +1100 [thread overview]
Message-ID: <20151217042613.7581.1566.stgit@noble> (raw)
If rpc.statd is temporarily unresponsive (e.g. because DNS service is
slow) it can cause mount attempts to fail inappropriately or can cause
multiple rpc.statd processes to be running on the one machine.
These patches address those problems.
---
NeilBrown (2):
mount.nfs: trust the exit status of "start_statd".
start-statd: don't run multiple rpc.statds on the one host.
utils/mount/network.c | 6 +++++-
utils/statd/start-statd | 8 ++++++++
2 files changed, 13 insertions(+), 1 deletion(-)
--
Signature
next reply other threads:[~2015-12-17 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 4:27 NeilBrown [this message]
2015-12-17 4:27 ` [PATCH 1/2] mount.nfs: trust the exit status of "start_statd" NeilBrown
2015-12-17 4:27 ` [PATCH 2/2] start-statd: don't run multiple rpc.statds on the one host NeilBrown
2016-01-16 21:58 ` [PATCH nfs-utils 0/2] Fix problems caused by rpc.statd being unresponsive Steve Dickson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151217042613.7581.1566.stgit@noble \
--to=neilb@suse.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).