From owner-freebsd-bugs Tue Nov 14 3:30: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C225937B479 for ; Tue, 14 Nov 2000 03:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id DAA18010; Tue, 14 Nov 2000 03:30:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 14 Nov 2000 03:30:04 -0800 (PST) Message-Id: <200011141130.DAA18010@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Harald Hanche-Olsen Subject: Re: kern/22826: Memory limits have no effect in linux compatibility Reply-To: Harald Hanche-Olsen Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/22826; it has been noted by GNATS. From: Harald Hanche-Olsen To: bde@zeta.org.au Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/22826: Memory limits have no effect in linux compatibility Date: Tue, 14 Nov 2000 12:24:32 +0100 + Bruce Evans : | On Mon, 13 Nov 2000 hanche@math.ntnu.no wrote: | | > Set a low memory limit. Soft or hard, it doesn't matter: | > $ ulimit -H -m 8192 | | I think you want to use -d (data segment size) and maybe -s (stack | size) instead of -m (max memory size) (better described as max | resident set in setrlimit(2)). -m limits use of real memory but | doesn't limit use of virtual memory. Oh, I didn't know that. (In fact, it's a bit tricky to correlate the limits described in setrlimit(1) with those handled by the (u)limit command in various shells. More to the point, however, in my experiment I used both -d and -s as well as -m, and still the process grew without bound. I'm sorry, I should have mentioned that. - Harald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message