[EMAIL PROTECTED] (John Hascall) writes:
>Marcus Watts <[EMAIL PROTECTED]> wrote:
>}> > I am seeing that if a process holds an AFS file open, and that
>}> > file is deleted externally, that eventually the process can no longer
>}> > read the file.
... stuff deleted ...
> Actually, I believe NFS handles the "temp file" case correctly --
> if you delete a file which you have open the NFS client renames
> the file to one of those funky .nfs############# files and
> deletes that when you close it. This frees the server from
> having to keep state in this case.
NFS Only handles this correctly if you delete the file from the client
which has the file open. If you delete it from another machine, the
file goes away, and you will get a stale file handle. The original
poster was talking about a file which is "deleted externally". I don't
know whether he meant from another process on the same client (which
NFS handles pseudo-correctly, with the above hack), or from another
client (which NFS doesn't handle correctly).
I believe that for afs, anonymous files are fixed in afs 3.4, you'll
have to ask transarc about how it supports the various permutations
above.
