From: "Ragnar Kjørstad" <nfs@ragnark.vestdata.no>
To: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] STATD - SM_NOTIFY have wrong ID_NAME on multihost servers.
Date: Wed, 24 Nov 2004 00:26:36 +0100 [thread overview]
Message-ID: <20041123232636.GE19342@vestdata.no> (raw)
In-Reply-To: <41A39D57.8060902@RedHat.com>
On Tue, Nov 23, 2004 at 03:28:07PM -0500, Steve Dickson wrote:
> Here is a patch that make sure the correct hostname is used
> in the SM_NOTIFY message what is sent from a rebooted server
> that has multiple network interfaces.
>=20
> Using the network part of the destination address, the correct network
> interface is found. Then a gethostbyaddr() on that interface is done,
> which yields the correct hostname that should be sent in the notify
> message....
>=20
> Comments?
It has been a while since I looked at this code, but:
1. What happens when you run statd with the "-n" option?
Does this patch override the name the user gave?
2. Does this really find the correct hostname?
If I'm not mistaken, the nfs client needs to get a SM_NOTIFY message
with the hostname that it actually mounted from, right?
This may or may not match the hostname that the server find when
running gethostbyaddr on the interface's IP, so one can easily find
scenarios where this patch will cause statd to stop working.
Now, there new behavious may actually be better, but I'm not sure
it's acceptable to change it anyway?
Could an alternative be to send out SM_NOTIFY messages for multiple
hostnames? Both the one from gethostname() and the ones found by
reverse lookup from the interfaces? Then I guess the meaning of the
"-n" option could be changed to _add_ a hostname to the list of
names to broadcast for?=20
--=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
next prev parent reply other threads:[~2004-11-23 23:26 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 [this message]
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
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=20041123232636.GE19342@vestdata.no \
--to=nfs@ragnark.vestdata.no \
--cc=SteveD@redhat.com \
--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.