Well said - in my bad old solaris 2.6 days we used automounter maps to get round the problem of a "downed" NFS server hanging the solaris clients. There's autofs for Linux, but I'm not sure how robust it is - any feedback anyone? Of course, there is the argument that when you have all your files on a central NFS server, if it hangs you couldn't possibly do anything useful with the clients anyway, but I think that's a cop-out. You'd like the NFS server to re-establish connections to the clients once it's back up, but I guess that's in the realms of kernel software development and other scary stuff and the like ;) Just my 2p's worth. Cheers, Jon David Krider wrote:
Örn Einar Hansen wrote:
Þann Mánudagur 03 janúar 2005 04:51 skrifaði elefino:
I've added a second Linux box to my little network. It was stated in a previous thread in this list that SAMBA3 is basically just as good as NFS for file and printer sharing... so, with that advice (to somebody else) I'll stick with SAMBA (that I already use for sharing with the Windows box).
Whoever told you that Samba3 was as good as NFS for file and printer sharing, is about as wrong as he could ever be. There are real differences between a CIF share and a NFS share, and then you add the fact that Samba is basically an attempt to "emulate" the CIF share on Linux, and thus not as good as a true Windows box is.
Want to know the single best way to hang a Unix box so badly as to need a reboot? Down a box it has an NFS connection to. Simple as that. Works every time, unless you've mounted the share with lots of options that might cause data loss. And sometimes it's pretty dang inconvenient. Don't get me wrong. I understand why, and I even appreciate it. But there are different ways of doing things for different purposes, and NFS isn't and end-all-be-all file serving solution. Feel free to pick whatever works for you. (And if everything I read about AFS didn't scare me away from it, I'd probably try it.)
dk