Hi Ben,
On Sat, Mar 19, 2022 at 08:58:46PM +0100, Ben Hutchings wrote:
> I'm not sure that this bug was ever fixed.
>
> nfs-utils actually uses nfs_getport() to get the port. That passes a
> timeout of {-1, 0} to libtirpc, which is invalid and should result in
> using the rpcbind client's default timeout.
>
> The TCP client interface is implemented in src/clnt_vc.c. It has a
> default timeout (ct_wait field) that can be set with CLNT_CONTROL(...,
> CLSET_TIMEOUT, ...), but nfs-utils doesn't seem to do that. So it
> seems like there is a default timeout of 0!
Is this still something we need to report upstream? (And if so, could
you do it?).
Regards,
Salvatore
