Comment 6 for bug 540637

Wow, wrote this late at night, and realized that last part is not very clear.

From a cold boot under lucid, I have two machines that are nfs clients to this machine. One running OSX 10.6, and one running 10.5 (all with the latest software updates, etc.).

The 10.6 machine works right out of the blocks, and gives no mention in syslog about any traffic or issues.

The 10.5 machine is the one with the problems. I have to do the above workarounds to get it to behave at all. If I try to access my nfs shares before I run the workaround (straight after booting, for example), my syslog is filled with commands like this:

May 3 22:38:55 luka-beast mountd[1268]: authenticated mount request from 192.168.1.101:979 for /media/music-n-vids (/media/music-n-vids)
May 3 22:39:35 luka-beast kernel: [ 230.030039] statd: server rpc.statd not responding, timed out
May 3 22:39:35 luka-beast kernel: [ 230.030062] lockd: cannot monitor luka-laptop.local
May 3 22:40:05 luka-beast kernel: [ 260.030036] statd: server rpc.statd not responding, timed out
May 3 22:40:05 luka-beast kernel: [ 260.030058] lockd: cannot monitor luka-laptop.local
...

And eventually my nfs connection drops, until the OS or anything else touches the mount, then automount kicks in and it starts all over again.

When I run the workaround above, I see this:
May 3 22:44:05 luka-beast kernel: [ 500.031644] nfsd: last server has exited, flushing export cache
May 3 22:44:07 luka-beast kernel: [ 502.831630] svc: failed to register lockdv1 RPC service (errno 97).
May 3 22:44:07 luka-beast kernel: [ 502.832407] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
May 3 22:44:07 luka-beast kernel: [ 502.832428] NFSD: starting 90-second grace period

And then that's it. No messages from lockd, statd, or mountd. And everything runs smoothly on both machines.

Might be a clue, but sounds more like another manifestation of the symptom.