Date: Mon, 6 Mar 95 10:07:16 MST From: terry@cs.weber.edu (Terry Lambert) To: davidg@Root.COM Cc: phk@ref.tfs.com, jhay@mikom.csir.co.za, current@FreeBSD.org Subject: Re: "Text file busy" with program not running anymore? Message-ID: <9503061707.AA18314@cs.weber.edu> In-Reply-To: <199503052133.NAA00248@corbin.Root.COM> from "David Greenman" at Mar 5, 95 01:33:08 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> No. Executed mapped files are a special case. I actually think that the > "text file busy" thing is generally a hack that should just be removed. I can > see no valid justification for preventing writes to executing files. If you > really don't want your executing process(es) to die, then unlinking the file > first is this the thing to do. Deovercommitting the image, since it is possible, is the thing to do. ENOMEM is the correct hack. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9503061707.AA18314>