[lkml]   [1996]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Path: not-for-mail
    From: Olaf Titz <>
    Subject: Re: Linux 2.0.0 fails to return Text File Busy for .so files
    Message-ID: <>
    Date: 20 Jun 1996 10:31:55 +0200
    References: <>
    Organization: private Linux site, southern Germany
    Lines: 26

    Systemkennung Linux <> 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
    > 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/* 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. :-)

    ___ or @{stud,informatik} ____
    __ o <URL:> <IRC:praetorius>
    __/<_ >> Just as long as the wheels keep on turning round
    _)>(_)______________ I will live for the groove 'til the sun goes down << ____

     \ /
      Last update: 2005-03-22 13:37    [W:0.017 / U:7.216 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site