fmd should make sure it is registered with rpcbind
In a case the rpcbind restarts, the fmd looses its registration with it (see #5611 for the example). Since fmd is system critical service, we do not want to restart it when absolutely not needed. So we need to find another solution for fmd to make sure the fmd is still registered (or re-registered) with rpcbind in a case the rpcbind restarts.
From an email from Robert Mustacchi:
I don't have first hand knowledge of this, so I'm mostly trying to put it together. But part of fmd's purpose is to diagnose faults that occur. When services restart for whatever reason, that information is sent off to fmd as part of diagnosis by startd/configd. Say you had a pathological rpcbind, you wouldn't want those errors causing fmd to restart and making it harder to actually diagnose the failure that's going on. So, in this case, it seems like given fmd's purpose, we shouldn't be restarting and should file an RFE to implement the poll or think about some other mechanism.