From owner-freebsd-current  Tue Jan  6 16:37:56 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA12668
          for current-outgoing; Tue, 6 Jan 1998 16:37:56 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA12654
          for <freebsd-current@FreeBSD.ORG>; Tue, 6 Jan 1998 16:37:45 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id QAA05669; Tue, 6 Jan 1998 16:36:37 -0800 (PST)
To: pb@fasterix.freenix.org (Pierre Beyssac)
cc: freebsd-current@FreeBSD.ORG
Subject: Re: funny ETXTBSY problem 
In-reply-to: Your message of "Tue, 06 Jan 1998 21:27:39 +0100."
             <19980106212739.HR12419@@> 
Date: Tue, 06 Jan 1998 16:36:36 -0800
Message-ID: <5665.884133396@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I just noticed the following problem: you can't copy over an
> executable after it has been run once since boot time.
> 
> This is fairly easy to reproduce:
> 
> $ cp /bin/sh /tmp
> $ echo echo hello there | /tmp/sh
> hello there
> $ cp /bin/sh /tmp
> cp: /tmp/sh: Text file busy

Interesting.  I don't see this behavior with my Dec 22nd kernel, so
it must have come in after that.  I did notice that the sticky
bit had interesting behavior, however, when I first tried this as
an average user:

jkh@whisker-> cp /bin/sh /tmp
jkh@whisker-> echo echo hello there | /tmp/sh
hello there
jkh@whisker-> cp /bin/sh /tmp
cp: /tmp/sh: Permission denied

Hmmm.  I thought it was only supposed to refuse this request if somebody
*else* tried to replace my file in /tmp! :-)

					Jordan