All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ragnar Kjørstad" <nfs@ragnark.vestdata.no>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: nfs@lists.sourceforge.net, nfs-admin@lists.sourceforge.net,
	Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH] STATD - SM_NOTIFY have wrong ID_NAME on multihost servers.
Date: Wed, 24 Nov 2004 21:35:24 +0100	[thread overview]
Message-ID: <20041124203524.GJ19342@vestdata.no> (raw)
In-Reply-To: <OFB654AEC9.6741BC01-ON88256F56.006576D7-88256F56.0066D21B@us.ibm.com>

On Wed, Nov 24, 2004 at 10:43:04AM -0800, Marc Eshel wrote:
> > "10.0.0.1" is a character string as much as any - unless the
> > specification says something more about this?
>=20
> That would help statd that is running in the kernel and can not do
> gethostbyname(). The problem right now is that the kernel statd ignores=
 the
> mon_name in the notify msg altogether and uses the uses the source IP
> address from the RPC request. It would be nice if we send the notify ms=
g
> from the same source as is specified in the -n option. This way what ev=
er
> the client uses will result in the same the IP.
> see:
>       http://marc.theaimsgroup.com/?l=3Dlinux-nfs&m=3D110064006512730&w=
=3D2

Yes, let me adjust my proposal:

And I think that could be something along the lines:

* loop over all available interfaces
* for each interface, send a message to all clients that belong on
  this subnet
* the message could be based on the IP or gethostbyaddr(IP).
+ make sure the outgoing message is sent from the interface it
  applies to, so that it works with clients that look at the
  source address instead of the name. (or look at both, but only
  accept the message if they match).


I think this would cover absolutely all cases (with the exception of
source NAT, and that's pretty obscure!?), so I think it's fair to remove
"-n". (rather, it should give the user a message the option is obsolete
and is beeing ignored)


OK, so I didn't actually look closely at the code to if this could be
easily coded, but how hard can it be? :-)


--=20
Ragnar Kj=F8rstad
Software Engineer
Scali - http://www.scali.com
High Performance Clustering


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-11-24 20:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 20:28 [PATCH] STATD - SM_NOTIFY have wrong ID_NAME on multihost servers Steve Dickson
2004-11-23 23:26 ` Ragnar Kjørstad
2004-11-24  0:46   ` Steve Dickson
2004-11-24  2:00     ` Ragnar Kjørstad
2004-11-24 12:00       ` Steve Dickson
2004-11-24 17:35         ` Ragnar Kjørstad
2004-11-24 18:43           ` Marc Eshel
2004-11-24 20:35             ` Ragnar Kjørstad [this message]
2004-11-24 22:08           ` Steve Dickson
2004-11-24 23:25             ` Ragnar Kjørstad
2004-11-26 13:01               ` Steve Dickson
2004-11-24  4:42     ` Marc Eshel

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=20041124203524.GJ19342@vestdata.no \
    --to=nfs@ragnark.vestdata.no \
    --cc=SteveD@redhat.com \
    --cc=eshel@almaden.ibm.com \
    --cc=nfs-admin@lists.sourceforge.net \
    --cc=nfs@lists.sourceforge.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.