From owner-freebsd-current Thu Oct 15 10:25:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25575 for freebsd-current-outgoing; Thu, 15 Oct 1998 10:25:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25544 for ; Thu, 15 Oct 1998 10:25:37 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.8.8) with ESMTP id NAA05676; Thu, 15 Oct 1998 13:25:11 -0400 (EDT) (envelope-from scrappy@hub.org) Date: Thu, 15 Oct 1998 13:24:57 -0400 (EDT) From: "Marc G. Fournier" To: Alfred Perlstein cc: freebsd-current@FreeBSD.ORG Subject: Re: Upping process limits... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wish...I'd also have to play with getting the right versions of CAM put into it and all that...I'll end up having to upgrade eventually, just was hoping to avoid for a couple of months :( Should I get rid of the *SIZ values altogether, in favor of login.conf, or is there a 'default ceiling' in place? On Thu, 15 Oct 1998, Alfred Perlstein wrote: > > you don't have a snap of that source code available to rebuild a kernel > from back then with? > > have you looked into using an earlier version of the sources? you're able > to ask for an older source tree by setting some flag in a cvsup file, > check the man page or the older lists. (i don't know how far back you can > go though) > > yes, you have a hard limit, yes you need a new kernel. > > -Alfred > > On Thu, 15 Oct 1998, Marc G. Fournier wrote: > > > > > I'm running a 3.0-current build of around the end of July this year, so > > pre-ELF stuff and have hit a snag... > > > > I need to increase the news processes datasize and stack limits, and can't > > seem to get them above 256Meg, even with modifying /etc/login.conf (and > > running cap_mkdb)... > > > > I had, at one point, added MAXDSIZ and DLTDSIZ values of 256Meg to my > > kernel, and suspect that this has created a *hard limit* to th emax,which > > login.conf can't override. Is this correct? > > > > If so, is there any way around this, without my having to rebuild? I've > > been putting off upgradeing to the current 3.0-ELF stuff for two > > reasons...fear and beign 2500kilometers away from the server :( > > > > Is there any sysctl value I can set or something like that? > > > > Thanks... > > > > Marc G. Fournier scrappy@hub.org > > Systems Administrator @ hub.org > > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message