From owner-freebsd-hackers Tue Jan 12 15:39:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04807 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:39:20 -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 PAA04802 for ; Tue, 12 Jan 1999 15:39:18 -0800 (PST) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.8.7/8.8.4) with SMTP id PAA21184; Tue, 12 Jan 1999 15:54:38 -0800 (PST) Date: Tue, 12 Jan 1999 15:54:38 -0800 (PST) From: Bernie Doehner To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: limiting per process swap space utilization like Solaris ulimit? In-Reply-To: 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 Tue, 12 Jan 1999, Bernie Doehner 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? Sorry, I should have said, I understand the reason for this (you cannot swap out more than entire size of the program). The question should rather have been, WHY/HOW can the value for swap space limitation not be reduced to less than data segment + stack? Bernie > Is this correct / valid for all shells (not just bash, which explicitly > prints this out as the per process swap space limitation)? > > Thanks. > > Bernie > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message