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
