Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ucsd!rutgers!psuvax1!schwartz@shire.cs.psu.edu From: schwartz@shire.cs.psu.edu (Scott Schwartz) Newsgroups: comp.unix.wizards Subject: NFS (was Re: Making rm undoable) Message-ID: <4404@psuvax1.cs.psu.edu> Date: 27 Mar 89 03:54:23 GMT References: <6805@phoenix.Princeton.EDU> <7360@phoenix.Princeton.EDU> <10113@bloom-beacon.MIT.EDU> Sender: news@psuvax1.cs.psu.edu Reply-To: schwartz@shire.cs.psu.edu (Scott Schwartz) Distribution: usa Organization: Pennsylvania State University, Computer Science Lines: 19 In-reply-to: hedrick@geneva.rutgers.edu (Charles Hedrick) In article , hedrick@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