From owner-freebsd-current Mon Mar 6 09:14:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA11796 for current-outgoing; Mon, 6 Mar 1995 09:14:08 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA11790 for ; Mon, 6 Mar 1995 09:13:59 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18252; Mon, 6 Mar 95 10:05:40 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503061705.AA18252@cs.weber.edu> Subject: Re: "Text file busy" with program not running anymore? To: davidg@Root.COM Date: Mon, 6 Mar 95 10:05:39 MST Cc: mark@grondar.za, phk@ref.tfs.com, jhay@mikom.csir.co.za, current@FreeBSD.org In-Reply-To: <199503052143.NAA00266@corbin.Root.COM> from "David Greenman" at Mar 5, 95 01:43:13 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > 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... Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.