>>>>> " " == Bernd Eckenfels <[EMAIL PROTECTED]> writes:
>> Why in hell are library open for write? But it doesn't seem to
>> be only libraries:
> They are not open for write. They are open for mmaped read. The
> Problem with this is, that as long as the files are open, the
> filesystem cannot remove them from disk. This means, that as
> long as you have files open, even for read, which are deleted,
> a remount ro will fail.
> The new lsof will find those mmaped files, so you can simply
> restart the associated binary.
Ah, I see. Forgot about that.
Maybe the kernel coud swap in the deleted libraries and keep it in
memory or real swap from then on instead of blocking the fs.
> Yes, all daemons will get started with the old libs, since a
> upgrade always happens after system start :) But not only
> daemons. Think of Shells, getty, login, ...
So, when you update glibc, / can't be remounted ro any more?
Ugly.
MfG
Goswin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
