On Wed, 16 Feb 2000, Benjamin Scott wrote: > But I *don't* expect a loss of connectivity to result in the widespread > destruction of the filesystem on the server! That's ridiculous! (However, as > a long-time computer user, I have learned that "ridiculous" and "reality" are > far from mutually exclusive...) Heheh... two words: Microsoft Windows. 'Nuff said. > > If the write was modifying the inode table (I have no idea how this is > > handled on NFS...) then I imagine it's possible that you'll hose the FS. > > Ugh. I was hoping that NFS didn't go that low-level, but given the fact > that NFS has been moved into the kernel with Linux 2.2 ... blech. I don't know that it does; WRT that one point, I was only pointing out that the possibility exists. I've looked at very little source code in the kernel, and only slightly more code in userland apps... I don't know how it's implemented. [Probability afficionados will point out that the probability is really either 1 or 0, depending on the implementation... but as Mulder said, "Scully, no one likes a math geek."] > > if you're paging in a swapped process on some systems, they will re-read > > the text segment from the disk ... and if the system loses contact with > > the server that the executable was shared from, it will cause > > system-dependent problems ranging from swap errors to kernel panic. > > Double ugh. Nice error recovery there -- NOT! I've noticed that there Could be worse... more often than not my Windows machine just freezes indefinitely, with no indication of why, when a problem occurs. Talk about your error recovery disasters! I only use it for playing games, not serious work... heheh > seems to be an "error threshold" in Unix. Up to a certain point, everything > works fine, but if things get hosed badly enough, the system just throws up > its hands and says "I give up!". Linux doesn't seem to do that as often as > the commercial Unixes; one of the (many) things I like about it. :-) I'm inclined to agree. Seems there really is a benefit to having thousands of people looking at the code, for no other reason than they really want it to be better! 8^) But try selling that to your PHBs.... heheh > Oh, well. Mucho thanks for the good info, Derek. I think I'll add that NFS > book from O'Reilly to my To-Buy list.... :-) Just save yourself some time and go buy the whole collection of O'Reilly books. They're expensive but they're (mostly) worth it. However, I will comment that this particular volume is "Managing NIS and NFS" and the NIS portion is so outdated as to be almost, but not entirely, utterly useless. For those in the book-buying mood, I also highly, highly recommend _Unix System Administration Handbook_, Evi Nemeth et. al. It's getting a bit old, but it's still the book I refer to the most. It's the one with the bright red cover, or as I like to refer to it, "the other red book". -- "Quis custodiet ipsos custodes?" "Who watches the watchmen?" -Juvenal, Satires, VI, 347 Derek D. Martin | Senior UNIX Systems/Network Administrator Arris Interactive | A Nortel Company [EMAIL PROTECTED] | [EMAIL PROTECTED] ------------------------------------------------- ********************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **********************************************************
