Date: Wed, 7 Jan 1998 14:51:18 +1100 (EST) From: John Birrell <jb@freebsd1.cimlogic.com.au> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: pb@fasterix.freenix.org, freebsd-current@FreeBSD.ORG Subject: Re: funny ETXTBSY problem Message-ID: <199801070351.OAA10822@freebsd1.cimlogic.com.au> In-Reply-To: <5665.884133396@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 6, 98 04:36:36 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan K. Hubbard wrote: > > 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 At Dec 30, I have seen that. I didn't mention it because of John Dyson's warnings. After building from the 'fixed' sources, I haven't seen the problem. I'll go back to building the ports tree... that'll find it if it is still a problem. Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801070351.OAA10822>