Systemkennung Linux <linux@mailhost.uni-koblenz.de> wrote:
> > think if a shared library is busy, any attempt to modify it should return
> > ETXTBSY, right?
To write it, yes. To unlink it, no - as with application binaries.
> Zzzzt - and you can't replace your libraries anymore because at least libc.so
> is almost always in use.
Unless your init is linked statically (IMHO a stupid idea), it is
_always_ in use.
> It's ok to unlink(2) (rm) a library because as long as the library's inode
> is still open you the file is still accessible and that's what the current
> code does. You just shouldn't do something like rm /lib/libc.so* but
> install the new library which uses a different filename, run ldconfig,
> then rm the old, now unnecessary library file.
Right. But it will keep its disk blocks until the next reboot. :-)
olaf
-- ___ Olaf.Titz@inka.de or @{stud,informatik}.uni-karlsruhe.de ____ __ o <URL:http://www.inka.de/~bigred/> <IRC:praetorius> __/<_ >> Just as long as the wheels keep on turning round _)>(_)______________ I will live for the groove 'til the sun goes down << ____