From owner-freebsd-questions@FreeBSD.ORG Mon Mar 12 19:14:03 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F87716A401 for ; Mon, 12 Mar 2007 19:14:03 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 545E813C465 for ; Mon, 12 Mar 2007 19:14:03 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay5.apple.com (relay5.apple.com [17.128.113.35]) by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l2CJE3B8007594; Mon, 12 Mar 2007 12:14:03 -0700 (PDT) Received: from relay5.apple.com (unknown [127.0.0.1]) by relay5.apple.com (Symantec Mail Security) with ESMTP id 0D01C29C005; Mon, 12 Mar 2007 12:14:03 -0700 (PDT) X-AuditID: 11807123-9f920bb000004462-83-45f5a67b0bf7 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay5.apple.com (Apple SCV relay) with ESMTP id 021B330400C; Mon, 12 Mar 2007 12:14:03 -0700 (PDT) In-Reply-To: References: <6.0.0.22.2.20070309094909.024c9dd0@mail.computinginnovations.com> <6.0.0.22.2.20070309133935.024b8fd0@mail.computinginnovations.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8E7D8006-9480-4CF7-B670-1328BB881FCE@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Mon, 12 Mar 2007 12:14:02 -0700 To: Dima Sorkin X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-questions@freebsd.org Subject: Re: limitiation on memory allocation X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2007 19:14:03 -0000 On Mar 12, 2007, at 12:02 PM, Dima Sorkin wrote: > Something is probably wrong. > kern.dfldsiz on my machine does not influence. I don't believe you can change that value after the system has booted-- you have to set it either in the kernel's config file, or in /boot/loader.conf, for this to actually take effect. > I.e. after booting I run > $ limits > and it shows me the old 500M. > > Now, a point about 'maxdsiz'= 3.0-3.5G instead of 4G - this one I > must check. > I tried 3.9G :) Try using 3GB, agreed. Also, please note that the dftdsiz keyword affects the "hard" limit, not the "soft" limit...your shell might well have 500MB "soft" dsize limit by default, but would permit you to change that upward to the maximum set by the "hard" limit once you've changed that value. See "man getrlimit": A resource limit is specified as a soft limit and a hard limit. When a soft limit is exceeded a process may receive a signal (for example, if the cpu time or file size is exceeded), but it will be allowed to con- tinue execution until it reaches the hard limit (or modifies its resource limit). The rlimit structure is used to specify the hard and soft limits on a resource, struct rlimit { rlim_t rlim_cur; /* current (soft) limit */ rlim_t rlim_max; /* maximum value for rlim_cur */ }; Only the super-user may raise the maximum limits. Other users may only alter rlim_cur within the range from 0 to rlim_max or (irreversibly) lower rlim_max. -- -Chuck