Bug#711021: mount.nfs timeout for GETPORT is much too short

2024-09-13 Thread Salvatore Bonaccorso
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 defaul

Bug#711021: mount.nfs timeout for GETPORT is much too short

2022-03-19 Thread Ben Hutchings
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 de

Bug#711021: mount.nfs timeout for GETPORT is much too short

2013-06-03 Thread Ben Hutchings
Package: nfs-common Version: 1:1.2.6-3 Severity: important This NFS client stopped being able to mount from my NFS server at boot time, around the time I upgraded them both to wheezy. I think the problem started when only the server was upgraded and was ultimately triggered by avahi-daemon being