Re: nfs in 2.0.33 ?

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sun, 12 Jul 1998 01:46:06 +0100 (BST)


> Solaris at least seems to put a .ns* file in directories it is writing

If you want Linux you'll also see .nfs* files occuring. What happens is
that many unix apps do this

fd=open(file, "blah", ..)
unlink("blah")

to get an open temporary file that has no name and dies when we exit. NFS
being stateless screws this up too, so all the NFS clients are hacked to
do a thing called "silly rename" when they rename files that are deleted
but open so that the server doesnt screw it up.

> Solaris also complains about absence of file locking on nfs directories
> imported from linux, no matter what I do vis a vis flock, etc.
> A little bird tells me it is related ...
> to over nfs. That may be putting thhe state back into stateless nfs.

File locking is a side item - knfsd does file locking, unfsd doesnt. Its
a seperate and differently broken protocol ;)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html