Date: Mon, 06 Mar 1995 10:22:15 -0800 From: David Greenman <davidg@Root.COM> To: terry@cs.weber.edu (Terry Lambert) Cc: current@FreeBSD.org Subject: Re: "Text file busy" with program not running anymore? Message-ID: <199503061822.KAA02179@corbin.Root.COM> In-Reply-To: Your message of "Mon, 06 Mar 95 10:05:39 MST." <9503061705.AA18252@cs.weber.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>> The VTEXT flag is only set on exec()'d files. Shared libraries aren't >> exec()'d. If you clobber the data in a shared library file, any processes >> which are currently using them will likely die. ...but install unlinks the >> target first, so this should happen. > >This still bugs the hell out of me. Clearly, if one of the dubious >"benefits" of memory overcommit (besides not being able to do decent >system dumps or software based power management) is the ability to >get "Text file busy" messages out the ying-yang, then you should get >them for any pages mapped as executable. > >And this includes shared libraries. > >WHY isn't the VTEXT flag set on anything mmap'ed as executable, like >shared libraries or dlopen targets? > >Enquiring minds want to know... The main reason is that mapping files with execute permission is too over- used. We could do this, but I suspect that it won't be a very popular change. -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503061822.KAA02179>