Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!ucbvax!ulysses!ulysses.att.com!ekrell From: ekrell@ulysses.att.com (Eduardo Krell) Newsgroups: comp.unix.internals Subject: Re: (was slashes, now NFS devices) Message-ID: <14400@ulysses.att.com> Date: 1 Mar 91 21:24:19 GMT References: <123382@uunet.UU.NET> <1991Feb22.141910.17013@decuac.dec.com> <124235@uunet.UU.NET> Sender: netnews@ulysses.att.com Organization: AT&T Bell Labs Lines: 17 In article thurlow@convex.com (Robert Thurlow) writes: >So how about telling us about some of them, rather than just ranting? >Maybe those of us who work with the NFS code can learn something new. How about this one: a client opens a file on a server to read from it. While the client is still reading from that file, the file gets unlinked by a process running in the server. It happens that this was the only link to the file. What happens when the client does the next read() ? What happens in the same situation where the process reading from that file is on the server? Hint: NFS is stateless ... Eduardo Krell AT&T Bell Laboratories, Murray Hill, NJ UUCP: {att,decvax,ucbvax}!ulysses!ekrell Internet: ekrell@ulysses.att.com