From owner-freebsd-current Fri Jun 7 19:57:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA25064 for current-outgoing; Fri, 7 Jun 1996 19:57:50 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA25055 for ; Fri, 7 Jun 1996 19:57:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id TAA12115; Fri, 7 Jun 1996 19:57:28 -0700 (PDT) Message-Id: <199606080257.TAA12115@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Michael L. VanLoon -- HeadCandy.com" cc: "John S. Dyson" , freebsd-current@freebsd.org Subject: Re: More on VM, swap leaks In-reply-to: Your message of "Thu, 06 Jun 1996 16:06:24 PDT." <199606062306.QAA06882@MindBender.HeadCandy.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 07 Jun 1996 19:57:28 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >>> It does install with the sticky bit set, but I thought that modern >>> Unices ignored it as they try to keep everything in swap for as long >>> as possible. > >>The VM system totally ignores the sticky bit for executables. > >I had always suspected as much. Thanks for confirming this. (Is this >in 4.4BSD in general, or in FreeBSD, specifically?) It's only relavent to the old 4.3BSD VM system. When it got thrown out for the Mach stuff in the "Net" release, the sticky bit on executables went with it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project