On Wed, 16 Feb 2000, Paul Lussier wrote: > > In a message dated: Tue, 15 Feb 2000 23:44:00 EST > Benjamin Scott said: > > comes back. In theory this is a good thing, though, as Derek pointed > out, in reality it too can cause problems. What if you're trying to > move a filesystem from one server to another? You essentially have no > choice but to reboot all the clients, since the hard option will hang > them, and when the fs comes back on line, they'll get "Stale NFS > Filehandle" errors. This can be HELPED (notice I did not say fixed...) by using the intr option. It's better than rebooting, but it still isn't ideal. I don't know that there's any good way around that though... > NFS is absolutely the worst possible solution...except for all the rest :) Heheh... yeah. > Well, keep in mind that todays corporate culture heavily utilizes laptops > which now come with 8 and 13 GB harddrives. People like managers, > sales/marketing, executives, etc., all travel quite frequently. A > distributed, caching fs technology would solve a lot of problems for both > them, and us IT people. It would allow for the instantaneous sync'ing of the > laptop with the network once it were re-connected with the local LAN, and > allow the backup of the laptop data! This is a huge win for many people. > Unfortunately, we're stuck with the limitations of NFS because it's an > industry standard, and there's no demand for anything else :( Sounds good... So when are you going to write one? :) -- "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 **********************************************************
