All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 25 Nov 2004 00:25:31 +0100	[thread overview]
Message-ID: <20041124232530.GL19342@vestdata.no> (raw)
In-Reply-To: <41A5064B.1030009@RedHat.com>

On Wed, Nov 24, 2004 at 05:08:11PM -0500, Steve Dickson wrote:
> Ragnar Kj=F8rstad wrote:
> >On Wed, Nov 24, 2004 at 07:00:08AM -0500, Steve Dickson wrote:
> >>No, since the spec says a the id_mon needs to be character string....
> >
> >"10.0.0.1" is a character string as much as any - unless the
> >specification says something more about this?
>
> Well here is what the spec says wrt to mon_names:
> "For maximum portability and interworking, it is recommended that=20
> applications
> and users define host names containing only the characters of the Porta=
ble
> Filename Characters defined in ISO/IEC 9945-1:1990."
>=20
> So doing some like would probably cause interopability issues with othe=
r
> OSes....

Well, I don't have the ISO/IEC 9945-1:1990 easily available, but I have
a hard time imagining a standard for Portable Filename Characters that
don't include number and '.'.

However, if it's possible that it will create compabilityproblems,
you're probably right - it's not worth the effort. After all, it only
matters if you have inconsistencies in your name-resolution system.=20


> >In short, this is exactly like what your patch does except that:
> >- if there are multiple matching interfaces (e.g. aliases) we
> > send messages for all
>
> Yes see your point, but is aliasing all that common in non-HA environme=
nts?
I don't have any statistics on that, but I don't think it's totally
unheard of :)

> The relatively simple  patch I'm proposing is a small step in the right=
=20
> direction which would make statd work correctly on multihome servers.

Yes, I think it is.

> Should we strive to make statd more HA friendly, YES!  but I would
> suggest one step at time.... Meaning we should propose this match to Ne=
il
> for inclusion in upstream and then build on it... imho...

I have no problem with that.
I had just hoped I could trick you into fixing one more thing once you
were on a roll :-)


--=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 23:25 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
2004-11-24 22:08           ` Steve Dickson
2004-11-24 23:25             ` Ragnar Kjørstad [this message]
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=20041124232530.GL19342@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.