Re: [PATCH] STATD - SM_NOTIFY have wrong ID_NAME on multihost servers.

[Steve Dickson <SteveD@redhat.com>]

Ragnar Kj=F8rstad wrote:

>On Wed, Nov 24, 2004 at 07:00:08AM -0500, Steve Dickson wrote:
> =20
>
>>>If that's the case, are we allowed to just send the IP instead of the
>>>name?
>>>
>>>
>>>     =20
>>>
>>No, since the spec says a the id_mon needs to be character string....
>>   =20
>>
>
>"10.0.0.1" is a character string as much as any - unless the
>specification says something more about this?
> =20
>
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 Portabl=
e
Filename Characters defined in ISO/IEC 9945-1:1990."

So doing some like would probably cause interopability issues with other
OSes....

>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
> =20
>
Yes see your point, but is aliasing all that common in non-HA environment=
s?
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.
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 Neil
for inclusion in upstream and then build on it... imho...

SteveD.





-------------------------------------------------------
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