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

["Ragnar Kjørstad" <nfs@ragnark.vestdata.no>]

On Wed, Nov 24, 2004 at 07:00:08AM -0500, Steve Dickson wrote:
> >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....

"10.0.0.1" is a character string as much as any - unless the
specification says something more about this?



> >- If you have aliases (eth0, eth0:0) with different IPs but on the
> > same network. The current patch (if I read it correctly) will then
> > use the name from the last alias, which is kind of random.
>
> Well it would not be random, it would be the first interface....
>=20
> >The second case may be very relevant to the HA-problem which "-n" was
> >originally added for.
> >=20
> >
> Yes... the -n flag wold be the answer here...

Unless, of course, a more general fix would handle this automatically.

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


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
- I still don't understand why we don't send the IP instead of
  the name.


Unlike sending messages for all names to all clients it's not too
verbose.

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