steve-ss
When attempting to log into a server from a kdm login screen to an nfs server, the login stops part way through when loading kde from the server.
Several notes here: (1) The user does not log into the NFS server. He or she logs into the NFS client and accesses files in his or her home directory via NFS. (2) It's not the login process that stops, it's the KDE environment which doesn't start. The login process has already finished at this stage. (3) KDE is not loaded from the server, only the files in /home are accessed via NFS. I hope you see why some people are extremely confused by your description. To be a bit more constructive, here is a translation to language which I understand better: When a user starts a kdm session on a machine which mounts the /home directory from an NFS server, the KDE hangs in the initialization phase.
The error when doing a rcnfs reload is: /home: device is busy
Probably, there are blocked processes on the NFS client which access files on the NFS server. I'm not sure what "mount -a" does in this case, it may not be an error. Anyway, you may want to kill those blocked processes but not to re-mount the NFS filesystem. -- A.M.