Messages in this thread |  | | Date | Tue, 24 Sep 1996 11:25:52 +0200 (MET DST) | From | (Olaf Kirch) | Subject | Re: Ooooh that nfsd ... |
| |
In article <01BBA712.0495D9C0@alex.webexpress.net> you wrote: : My friend and I were looking at the same file on my Linux box. He used : vi and I used pico ... I was logged in directly and he was nfs-mounted : onto my HDD ... he saved the file and I exited pico w/out saving ... the : we tried to execute it and got the following? : : bash: ./filename : Text file is busy
This is OLD. I repeat OLD, and has been hashed out so many times.
When unfsd reads or writes a file, it has to open it. For performance reasons, the file handle is kept for several seconds, so that it doesn't have to open/close the file perpetually for each new request. After a few seconds of inactivity, the file is closed.
As I'm sure you know, the kernel will refuse to execute any binary or script that is still open for reading/writing.
: We renamed the filename and then ran it and it ran OK ... my guess : this is NFS related.
The rename operation didn't help a bit. The thing is, it took you a couple of seconds to rename the file, which was long enough for nfsd to close the file descriptor.
Olaf -- Olaf Kirch | NAK NAK NAKing on heaven's door... okir@monad.swb.de | Slowhand
|  |