Date: Thu, 4 Sep 2003 17:52:07 -0400 (EDT) From: Wesley Morgan <morganw@chemikals.org> To: "Scott M. Likens" <damm@fpsn.net> Cc: Paul Richards <paul@inty.com> Subject: Re: Text file busy Message-ID: <20030904174858.L78363@volatile.chemikals.org> In-Reply-To: <1062687770.45731.4.camel@acheron.livid.de> References: <1062686653.67807.77.camel@localhost> <1062687770.45731.4.camel@acheron.livid.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Sep 2003, Scott M. Likens wrote: > On Thu, 2003-09-04 at 07:44, Paul Richards wrote: > > Overwriting a file that's currently executing results in a "Text file > > busy" error. > > > > When did this start happening? > > > > This was something that was fixed way back on FreeBSD but it seems to be > > a problem again. > > > > Paul. > > this "feature" has always existed in FreeBSD for as long as I remember. > > Of course there are ways to bypass this "feature" but it's there for > your protection. You shouldn't be upgrading a program that's in > resident memory. That's like trying to reinstall X while running in X. > You're just asking for problems. > > turnoff postfix, install the new version and be happy. > > Every single 'flavor' of Unix/Unices has always had this feature. I've > seen it on HP-UX box's on Solaris Servers, Linux, NetBSD, OpenBSD, > FreeBSD. Maybe you wern't paying attention but, that is one of those > things I think should fall under duh, i shouldn't do that it might make > things crash hard. It's also unfortunate that this protection does not seem to extend to libaries. I've had some in-use X libraries get overwritten with some very colorful results. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030904174858.L78363>