From owner-freebsd-hackers Tue Jan 12 15:36:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04595 for freebsd-hackers-outgoing; Tue, 12 Jan 1999 15:36:44 -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 PAA04586 for ; Tue, 12 Jan 1999 15:36:42 -0800 (PST) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.8.7/8.8.4) with SMTP id PAA21176; Tue, 12 Jan 1999 15:52:03 -0800 (PST) Date: Tue, 12 Jan 1999 15:52:03 -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: <199901121757.JAA05222@apollo.backplane.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 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? 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