Frank van der Linden <frank@wins.uva.nl> writes:

> > I have a 1.3-current box (as of about a month ago) which has never
> > been able to use amd to mount my 1.3.3-ish box using AMD.  Not using
> > AMD (the mount command directly) works perfectly.
> 
> There is a problem with amd, because it uses TCP for mounts, and is
> likely to dis- and reconnect a mount during its lifetime. This is
> more a TCP problem than an NFS problem. It was going to be fixed,
> but it hasn't happened yet so far. It'll be fixed before 1.4, I
> think.

No, the INITIAL mount fails, too.

run amd.
ls /net/moghedien/u0/ (hangs)
^C out of that.
kill amd.

If I re-run amd, the machine will lock fully on next access to
/net/moghedien/u0.  If I don't, it will lock at some later date.

--Michael