| Author |
Message |
Olaf van der Spek
Guest
|
Posted:
Tue Oct 19, 2004 12:27 am Post subject:
Why no Linux-like unlink behaviour of open files? |
|
|
Hi,
I was just wondering, why does NTFS not use Linux-like unlink behaviour
of open files?
Are there any advantages to the NTFS way? |
|
| Back to top |
|
 |
Andreas Nilsson
Guest
|
Posted:
Sun Oct 31, 2004 4:27 pm Post subject:
Re: Why no Linux-like unlink behaviour of open files? |
|
|
"Olaf van der Spek" <Olaf@XCC.TMFWeb.NL> skrev i meddelandet
news:OdpkTDVtEHA.904@TK2MSFTNGP11.phx.gbl...
| Quote: | Hi,
I was just wondering, why does NTFS not use Linux-like unlink behaviour
of open files?
Are there any advantages to the NTFS way?
|
The Windows NT has the advantage of letting the object manager (part of
os-kernel) to remove the file when the last reference of the file is closed.
This way, inherited file handles (to child processes) will have a consistent
way of accessing the file (the file won't simply dissapear when one process
marks the file as removed). |
|
| Back to top |
|
 |
Olaf van der Spek
Guest
|
Posted:
Thu Nov 04, 2004 9:26 pm Post subject:
Re: Why no Linux-like unlink behaviour of open files? |
|
|
Andreas Nilsson wrote:
| Quote: | "Olaf van der Spek" <Olaf@XCC.TMFWeb.NL> skrev i meddelandet
news:OdpkTDVtEHA.904@TK2MSFTNGP11.phx.gbl...
Hi,
I was just wondering, why does NTFS not use Linux-like unlink behaviour
of open files?
Are there any advantages to the NTFS way?
The Windows NT has the advantage of letting the object manager (part of
os-kernel) to remove the file when the last reference of the file is closed.
This way, inherited file handles (to child processes) will have a consistent
way of accessing the file (the file won't simply dissapear when one process
marks the file as removed).
|
That's no advantage, as Linux behaves in the same way.
The disadvantage of NT is that an external process can't mark the handle
as 'delete on (last) close'. |
|
| Back to top |
|
 |
|
|
|
|