Hi Ben,
On Wednesday 19 May 2010 05:44:56 Ben Hutchings wrote:
[...]
> > However, what isn't clear is why the client is calling the
> > Portmapper service since the port number has been supplied in the mount
> > options ("port=2049")
>
> [...]
>
> Right. For whatever reason, mount.nfs processes the options into a
> canonical form and at this point it will lose the port=2049 option.
> Please can you test the following patch:
[...]
Ah! That would explain it.
I've applied the patch and rebuilt mount.nfs. There's now no portmapper
interaction (when port=2049 is specified) and mounting the NFS server works
fine.
Many thanks!
Paul.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005191001.03889.paul.mil...@desy.de
