From: Mike Fedyk <mfedyk@matchmail.com>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Cyrille Beraud <cyrille.beraud@savoirfairelinux.com>,
linux-kernel@vger.kernel.org
Subject: Re: Removing an executable while it runs
Date: Wed, 5 Dec 2001 11:32:52 -0800 [thread overview]
Message-ID: <20011205193252.GB9050@mikef-linux.matchmail.com> (raw)
In-Reply-To: <B22D093570E@vcnet.vc.cvut.cz>
In-Reply-To: <B22D093570E@vcnet.vc.cvut.cz>
On Wed, Dec 05, 2001 at 05:15:52PM +0000, Petr Vandrovec wrote:
> On 5 Dec 01 at 11:00, Cyrille Beraud wrote:
>
> > I would like to remove an executable from the file-system while it is
> > running and
> > get all the blocks back immediately, not after the end of the program.
> > Is this possible ?
>
> No. Binary runs from these blocks. Maybe you can force it to run from
> swap by modifying these pages through ptrace interface, but it is
> not supported. Just kill the app if you need these blocks.
>
> > From what I understand, the inode is not released until the program
> > ends. Do all the file-systems behave the same way ?
>
> No. Some will refuse to unlink running app (or another opened file).
> Some will unlink it immediately, and app then dies when it needs
> page-in something. Some works as POSIX mandates.
>
POSIX behaviour would be in ext[23], reiserfs, xfs, (and probably ffs,
ntfs). Can someone verify which FSes have what behaviour?
I'd guess that vfat (fat16/28--err, 32), nfs, and hfs would delete
immediately.
mf
next prev parent reply other threads:[~2001-12-05 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 17:15 Removing an executable while it runs Petr Vandrovec
2001-12-05 19:32 ` Mike Fedyk [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 21:19 Petr Vandrovec
2001-12-05 16:00 Cyrille Beraud
2001-12-05 16:14 ` Brian Gerst
2001-12-05 20:00 ` Christopher Friesen
2001-12-05 20:54 ` Tim Walberg
2001-12-06 0:25 ` Jeff Dike
2001-12-06 15:43 ` Eric-Olivier Lamey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011205193252.GB9050@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=cyrille.beraud@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.