From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Ephase question.
Date: Tue, 13 Aug 2002 07:17:59 +0100 [thread overview]
Message-ID: <934f6b230a54710c86ea3b2502384e95@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
so if i completely remove a file that someone is executing, it continues to work,
but if i copy into a file that remains and someone is executing it, it fails.
makes perfect sense to me.
[-- Attachment #2: Type: message/rfc822, Size: 2627 bytes --]
From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Ephase question.
Date: Tue, 13 Aug 2002 02:13:08 -0400 (EDT)
Message-ID: <Pine.GSO.4.21.0208130206400.1501-100000@weyl.math.psu.edu>
On Tue, 13 Aug 2002, Russ Cox wrote:
> > > - Unix' solution of making the remove fail with "file busy"; it was
> > > always inconvenient and confusing. They use that one for in use
> > > executables.
> >
> > I haven't seen a version of unix do this one for a while (as in decades).
> > The remove succeeds, the file goes away when the last reference does (but
> > you have to have inodes ...). But maybe there is some version of Unix
> > you're referencing I'm not familiar with -- there's a lot of possibilities
> > out there nowadays ...
>
> i've seen it recently on either freebsd or linux,
> in the case of trying to remove or perhaps overwrite
> binaries that were being executed at the time.
> it was definitely a binary rather than a normal file.
Overwrite - sure. Remove - nope.
next reply other threads:[~2002-08-13 6:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 6:17 Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-14 14:12 Russ Cox
2002-08-14 13:19 rob pike, esq.
2002-08-15 8:59 ` Douglas A. Gwyn
2002-08-15 16:22 ` Ronald G Minnich
2002-08-13 23:49 rog
2002-08-13 17:28 Russ Cox
2002-08-13 17:01 rob pike, esq.
2002-08-13 16:37 anothy
2002-08-13 15:59 Russ Cox
2002-08-14 8:42 ` Douglas A. Gwyn
2002-08-13 15:57 Russ Cox
2002-08-13 15:43 rob pike, esq.
2002-08-13 13:13 rog
2002-08-13 12:16 presotto
2002-08-13 15:53 ` Ronald G Minnich
2002-08-13 11:43 David Gordon Hogan
2002-08-13 15:45 ` Ronald G Minnich
[not found] <rsc@plan9.bell-labs.com>
2002-08-13 5:42 ` Russ Cox
2002-08-13 5:53 ` Scott Schwartz
2002-08-13 6:05 ` Ronald G Minnich
2002-08-13 6:22 ` Alexander Viro
2002-08-13 6:13 ` Alexander Viro
2002-08-13 4:20 Russ Cox
2002-08-13 3:37 rob pike, esq.
2002-08-13 9:31 ` Douglas A. Gwyn
2002-08-13 3:33 presotto
2002-08-13 4:10 ` Alexander Viro
2002-08-13 5:39 ` Ronald G Minnich
2002-08-19 16:23 ` Boyd Roberts
2002-08-13 6:46 ` Andrew Lynch
2002-08-13 22:07 ` Roman V. Shaposhnick
2002-08-13 3:31 Russ Cox
2002-08-13 1:39 presotto
2002-08-13 3:14 ` Roman V. Shaposhnick
2002-08-13 1:26 Roman V. Shaposhnick
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=934f6b230a54710c86ea3b2502384e95@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).