sm-notify: IP vs hostname?

sm-notify: IP vs hostname?

[Eric Hagberg]

I've noticed that sm-notify pulls info from
/var/lib/nfs/statd/sm/$hostname files that also contain the IP address
that was in use when the lock(s) was created.

In cases where the hostname lookup may resolve to a different IP
address over time, would it make sense to try notifying the IP address
from that file rather than the hostname of the file? Or try the IP and
fall back to a hostname if the first fails (or just notify both?)?

Thanks,
-Eric

Re: sm-notify: IP vs hostname?

[Chuck Lever]

> On Oct 24, 2020, at 8:26 AM, Eric Hagberg <ehagberg@janestreet.com> wrote:
> 
> I've noticed that sm-notify pulls info from
> /var/lib/nfs/statd/sm/$hostname files that also contain the IP address
> that was in use when the lock(s) was created.
> 
> In cases where the hostname lookup may resolve to a different IP
> address over time, would it make sense to try notifying the IP address
> from that file rather than the hostname of the file? Or try the IP and
> fall back to a hostname if the first fails (or just notify both?)?

The historical tactic has been to send the notification to all the
addresses: for example, both IPv4 and IPv6. At first glance, it
seems like notifying both would be a useful behavior.


--
Chuck Lever