From owner-freebsd-questions@FreeBSD.ORG Thu Mar 10 21:46:45 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 545CF16A4CF for ; Thu, 10 Mar 2005 21:46:45 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6CF643D2D for ; Thu, 10 Mar 2005 21:46:44 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j2ALkikY001572; Thu, 10 Mar 2005 15:46:44 -0600 (CST) (envelope-from dan) Date: Thu, 10 Mar 2005 15:46:44 -0600 From: Dan Nelson To: "Chad Leigh -- Shire.Net LLC" Message-ID: <20050310214644.GH9663@dan.emsphone.com> References: <00ce60d0ae670341dbd028c4cab204ff@shire.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ce60d0ae670341dbd028c4cab204ff@shire.net> X-OS: FreeBSD 5.4-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: List Free Bsd Subject: Re: how to change process limits? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 21:46:45 -0000 In the last episode (Mar 09), Chad Leigh -- Shire.Net LLC said: > The following is aon 5.3-RELEASE-p5 > > If I do a limits command I get > > # limits > Resource limits (current): > datasize 524288 kb > stacksize 65536 kb > # > > However, login.conf has (and no other classes defined) > > default:\ > :datasize=unlimited:\ > :stacksize=unlimited:\ > > I am wondering where the datasize and stacksize get set. These have > limits when listed with "limits" but they do not appear to be getting > set through login as the login.conf has unlimitged. I believe those are extra-hard limits enforced by the kernel. You can raise them by adding this to /boot/loader.conf: kern.maxdsiz=2147483648 kern.maxssiz=2147483648 Then you can edit login.conf to set whatever soft and hard limits you want (remember to run "cap_mkdb /etc/login.conf" when you're done). I'm not exactly sure why those limits are boot-time tunables as opposed to regular sysctls, or why they exist at all. -- Dan Nelson dnelson@allantgroup.com