Start up OpenOffice from home directory (/h/users/krisa mounted over NFS).  Word
Processor opens with empty document.  Click "Open File" button in toolbar. 
OOffice locks up for 51 seconds, then the open dialog appears.

Current site design:

Hosts use amd for mounting NFS filesystems.  /h is a link to /net/phobos/h where
/net/phobos/h is a directory of symlinks to the proper /net/phobos/<filesystem>.

Under /h/users (/h/users -> /net/phobos/u) there are real directories and also
symlinks for users who exist at other sites.  You can have one user "krisa" who
has a real /h/users/krisa directory, and another user "foo" who's /h/users/foo
-> /net/otherlocationhost/h/foo.

My findings:

After the 51 seconds of lockup, I issue a "df" and notice amd has mounted a lot
of remote hosts.  It seems as if OOffice (even though starting in
/h/users/krisa) is dereferencing all the symlinks in /h/users, which is causing
amd to go out and mount the servers where these symlinks point to.

After opening up a .ppt file in /tmp, I have wanted to save it to
/h/users/krisa/doc and specified it by exact filename
(/h/users/krisa/doc/file.ppt) using "Save As", and it goes out and dereferences
everything under /h/users.  Sometimes this causes the system to freeze and lock
up due to the nature of NFS confusion, timeouts, and stale symlinks.

Tested systems are on RH7.2, amd v6.0.6, nfs-utils v0.3.1.  I tried this one two
hosts, similar configurations.