Ben Scott writes:
>
> On Tue, Feb 19, 2013 at 2:40 PM, Ken D'Ambrosio wrote:
> > If process A is reading from a file, and process B deletes it, process
> > A can continue to read from it until... well, until it stops reading
> > from it.
[...]
> > Can that space that the file takes up be overwrit
On Tue, Feb 19, 2013 at 2:40 PM, Ken D'Ambrosio wrote:
> If process A is reading from a file, and process B deletes it, process
> A can continue to read from it until... well, until it stops reading
> from it.
It can also seek it, write to it, etc. This condition persists
until the process cal
>Can that space that the file takes up be overwritten during
>this interim? Or does the OS hold the inode sacrosanct until
>both references AND processes are no longer making use of it?
Right - the OS's official record of a file's state is the
(in-memory copy of the) inode - the directory entri
Hey, all. For various esoteric reasons, I'm wondering if someone can
tell me the answer to this question.
If process A is reading from a file, and process B deletes it, process
A can continue to read from it until... well, until it stops reading
from it. Can that space that the file takes up
