Someone more adept in Linux/Unix internals can fill-in-the-blanks (or
correct me) here;
This is an implementation issue with the way in which files are mmap()'ed
from the backing
store into memory. Modifying the persistent bits on disk would invalidate
the memory map,
but removing it the file completely, while perhaps not desirable, would not
confuse the
run-time of that process to which it was associated (mapped).
--
Sean
____________________________________________________________________________________
Guennadi
Liakhovetski
<gl@dsa-ac.de> To
Sent by: <kernelnewbies@nl.linux.org>
kernelnewbies-bou cc
nce@nl.linux.org
Subject
"Text file busy"
04/15/2003 11:52
AM
Hello
There has been a discussion on the lkml some time ago, so, I thought, it
won't be too much OT to ask it here.
So, can anybody explain, what's the logic behind the behaviour - one can't
overwrite an existing running file, but can remove it? Is overwriting
re-uses the inode? And what's the result of that discussion about
overwriting shared libraries while they are in use?...
And, actually, why these questions arose - does anybody by chance have any
pointers to standard ways of updating running systems? For example, is
there somewhere a description of how Debian handles installation updates?
They seem to manage it pretty well...
Thanks
Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
