From owner-freebsd-hackers Tue Jan 12 16:51:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17988 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 16:51:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wireless.net (wireless.net [207.137.156.159] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17968 for ; Tue, 12 Jan 1999 16:51:12 -0800 (PST) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.8.7/8.8.4) with SMTP id RAA21479; Tue, 12 Jan 1999 17:06:32 -0800 (PST) Date: Tue, 12 Jan 1999 17:06:32 -0800 (PST) From: Bernie Doehner To: Terry Lambert cc: dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: limiting per process swap space utilization like Solaris ulimit? In-Reply-To: <199901130030.RAA15567@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 Jan 1999, Terry Lambert wrote: > > Why is it that under bash's ulimit -v, the swap space utilization is the > > sum of the data segment size and the stack size? > > Read-only pages don't need to be backed by swap? Actualy I already asked the very same question in a different forum. I assume the text segment is NOT swapped out because it is referenced way TOO often to be practical/efficient to swap out? > > Is this correct / valid for all shells (not just bash, which explicitly > > prints this out as the per process swap space limitation)? > > On machines where the program image is not used as a read-only > swap store, this would be different. You may have to install an > old copy of Xenix or SVR3.2 to find such a machine, though... > Actualy I think Solaris does this too.. Thanks. Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message