From: Michael Blandford <mlblandf@sedona.ch.intel.com>
To: jmoyer@redhat.com
Cc: autofs@linux.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: [RFC] rpc_ping and looong timeouts
Date: Mon, 07 Jun 2004 11:29:19 -0700 [thread overview]
Message-ID: <40C4B3FF.3060005@sedona.intel.com> (raw)
In-Reply-To: <16576.60526.394177.533027@segfault.boston.redhat.com>
Jeff Moyer wrote:
>This patch simply implements an icmp ping (code shamelessly stolen from
>clumanager), and does this before even attempting to do the rpc pings. If
>the icmp ping works, then we continue as usual. This takes care of the
>host down case quite nicely:
>
>
>
Would this patch cause problems for those of us who have icmp blocked?
If so, could we make it a run time option to enable/disable?
Michael
Disclaimer: The content of this message is my personal opinion only and
although I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak on
behalf of Intel on this matter.
next prev parent reply other threads:[~2004-06-07 18:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 20:30 [RFC] rpc_ping and looong timeouts Jeff Moyer
2004-06-04 1:17 ` Ian Kent
2004-06-04 19:06 ` Jeff Moyer
2004-06-04 21:41 ` Jeff Moyer
2004-06-05 2:08 ` raven
2004-06-06 2:18 ` Jeff Moyer
2004-06-05 5:36 ` raven
2004-06-06 3:00 ` Jeff Moyer
2004-06-06 3:13 ` raven
2004-06-06 3:57 ` Jeff Moyer
2004-06-07 18:29 ` Michael Blandford [this message]
2004-06-07 18:44 ` Jeff Moyer
2004-06-08 16:09 ` Michael Blandford
2004-06-08 16:15 ` raven
2004-06-08 16:26 ` Jeff Moyer
2004-06-08 16:36 ` raven
2004-06-08 17:25 ` Jeff Moyer
2004-06-08 17:51 ` Michael Blandford
2004-06-09 1:13 ` Ian Kent
2004-06-09 2:22 ` Jeff Moyer
2004-06-09 2:54 ` Ian Kent
2004-06-08 0:56 ` Ian Kent
2004-06-08 3:17 ` Peter C. Norton
2004-06-05 1:58 ` raven
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=40C4B3FF.3060005@sedona.intel.com \
--to=mlblandf@sedona.ch.intel.com \
--cc=autofs@linux.kernel.org \
--cc=jmoyer@redhat.com \
--cc=raven@themaw.net \
/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.