NFS (was Re: Making rm undoable)
Scott Schwartz
schwartz at shire.cs.psu.edu
Mon Mar 27 13:54:23 AEST 1989
In article <Mar.26.19.51.41.1989.8372 at geneva.rutgers.edu>, hedrick at geneva (Charles Hedrick) writes:
>You'll see that foo has been renamed to .nfsXXX. Now if you kill the
>tail, .nfsXXX will go away. I'm not sure quite how that interacts
>with statelessness. It's possible that if you open a file, remove it,
>and then crash before closing it, that the .nfsXXX file will stay on
>the the file server. I haven't looked at the code that carefully.
>From crontab:
find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
>Despite all the comments about how NFS violates "Unix semantics",
>we've not run into anything that failed across NFS, aside from bugs in
>implementations.
That's because of hacks like the above :-) NFS is stateless, except
for the state it maintains (on disk).
--
Scott Schwartz <schwartz at shire.cs.psu.edu>
More information about the Comp.unix.wizards
mailing list