From owner-freebsd-questions@FreeBSD.ORG Fri Apr 16 22:41:14 2004 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 8BC8D16A4CE for ; Fri, 16 Apr 2004 22:41:14 -0700 (PDT) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [202.0.58.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09F0643D39 for ; Fri, 16 Apr 2004 22:41:14 -0700 (PDT) (envelope-from markir@paradise.net.nz) Received: from smtp-2.paradise.net.nz (smtp-2b.paradise.net.nz [202.0.32.211]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0HWA00HSBVSP3O@linda-1.paradise.net.nz> for freebsd-questions@freebsd.org; Sat, 17 Apr 2004 17:41:13 +1200 (NZST) Received: from paradise.net.nz (203-96-145-185.adsl.paradise.net.nz [203.96.145.185]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id CE1289E267 for ; Sat, 17 Apr 2004 17:41:12 +1200 (NZST) Date: Sat, 17 Apr 2004 17:42:55 +1200 From: Mark Kirkwood In-reply-to: <4080B883.6090605@paradise.net.nz> Cc: freebsd-questions@freebsd.org Message-id: <4080C3DF.90605@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040404 References: <40807520.6070405@paradise.net.nz> <408077AD.4070203@paradise.net.nz> <4080B883.6090605@paradise.net.nz> Subject: Re: Increase max data segment size? 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: Sat, 17 Apr 2004 05:41:14 -0000 Yes there is, some more poking around in /usr/src/sys/kern/subr_param.c brought to light : maxdsiz = MAXDSIZ; TUNABLE_QUAD_FETCH("kern.maxdsiz", &maxdsiz); which looked suspicously like a kernel tunable for data segment size. So setting kern.maxdsiz in /etc/loader.conf seems to be the thing to do... Of course by this time I have managed to find some postings concerning MAXDSIZ and kern.maxdsiz. Hopefully the next person confused about this will find my postings *before* dredging the code! regards Mark Mark Kirkwood wrote: > > so is there any reason *not* to amend this and recompile? > > e.g. > > #define MAXDSIZ (1024UL*1024*1024) /* max data size now > 1G */ > > >