Clayton wrote:
OK, so all appeared to be working great. Then computer 2 was powered down. If I opened a file manager (or terminal window and did an ls -al) on computer 1, it appeared to hang the file manager. It just sat there blank.. and then after 20 minutes or more it finally timed out (?) and showed the contents of /home/$USER.
Is this normal? Shouldn't the intr option allow for the possibility of a NFS sever not being available, essentially pushing the mount attempts to the background, and silently mounting the NFS when the server comes available?
No, you're confusing it with soft. Reread the man page (e.g.): http://linux.die.net/man/5/nfs
Is this (using NFS server/client) a reasonable solution in a situation like this? Is there a better way to do this? (no central server, and wanting to share a partition on each drive across a small home network).
Well it's better not to design your network like this, with circular mounts, but it is possible.
Try a soft mount, if you expect the NFS server to be unavailable.
I tried that too with the same/similar results.... long timeouts/hangs in file managers and/or terminals that try to access /home/$USER or /media (where the NFS exports are mounted).
Hmm, you should see some change. Start again using soft mounts, don't use file managers for now, just command lines and please post the results of your commands and the relevant status messages in the logs. Also, if you're mounting from fstab and it's still not working, try setting the fstab line to noauto and then mount manually after booting completes. That may help to pinpoint the problem. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org