This is great for using something like this with the intent of one client where the server sends notification to one NFS client in one to one, many to one, or one to many configs, but in a larger environments, the NFS servers will be accommodating many hosts in a many to many arrangement. If there is more than one NFS server, I'm not sure, but does that mean there needs to be a fully meshed notify-forwarder mesh from where each NFS server needs to notify each NFS client. Managing a large number of notify-forwarder would get unwieldy and the problem of updating all the new servers. We support min 50 to easily over NFS servers that are in a continual being upgraded and changed. There is support for multiple paths from a single remote server,Feature request is to possibly auto identify all clients during client registration with NFS server, and notify all possible clients with ATTRIB event. On the flip side, I wonder with NFS server redundancy or load balancing (possibly balancer, DNS round robin, heartbeats, automounting or any number of other tricks where NFS Server IP is not necessarily fixed), does "watch -c " support hosts and/or DNS hostnames?
This is great for using something like this with the intent of one client where the server sends notification to one NFS client in one to one, many to one, or one to many configs, but in a larger environments, the NFS servers will be accommodating many hosts in a many to many arrangement. If there is more than one NFS server, I'm not sure, but does that mean there needs to be a fully meshed notify-forwarder mesh from where each NFS server needs to notify each NFS client. Managing a large number of notify-forwarder would get unwieldy and the problem of updating all the new servers. We support min 50 to easily over NFS servers that are in a continual being upgraded and changed. There is support for multiple paths from a single remote server,Feature request is to possibly auto identify all clients during client registration with NFS server, and notify all possible clients with ATTRIB event. On the flip side, I wonder with NFS server redundancy or load balancing (possibly balancer, DNS round robin, heartbeats, automounting or any number of other tricks where NFS Server IP is not necessarily fixed), does "watch -c " support hosts and/or DNS hostnames?