From: Steve Dickson <SteveD@redhat.com>
To: NeilBrown <neilb@suse.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH nfs-utils 0/2] Fix problems caused by rpc.statd being unresponsive.
Date: Sat, 16 Jan 2016 16:58:56 -0500 [thread overview]
Message-ID: <569ABD20.7040003@RedHat.com> (raw)
In-Reply-To: <20151217042613.7581.1566.stgit@noble>
On 12/16/2015 11:27 PM, NeilBrown wrote:
> 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.
Both patches committed.... again.. thank you!
steved
>
>
> utils/mount/network.c | 6 +++++-
> utils/statd/start-statd | 8 ++++++++
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> --
> Signature
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-01-16 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 4:27 [PATCH nfs-utils 0/2] Fix problems caused by rpc.statd being unresponsive NeilBrown
2015-12-17 4:27 ` [PATCH 2/2] start-statd: don't run multiple rpc.statds on the one host NeilBrown
2015-12-17 4:27 ` [PATCH 1/2] mount.nfs: trust the exit status of "start_statd" NeilBrown
2016-01-16 21:58 ` Steve Dickson [this message]
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=569ABD20.7040003@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.