From owner-freebsd-current Thu Apr 26 16: 7:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.phx.gblx.net (smtp10.phx.gblx.net [206.165.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 7A3F137B422 for ; Thu, 26 Apr 2001 16:07:09 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp10.phx.gblx.net (8.9.3/8.9.3) id QAA42896; Thu, 26 Apr 2001 16:07:07 -0700 Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp10.phx.gblx.net, id smtpdAm6kMa; Thu Apr 26 16:06:57 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA29635; Thu, 26 Apr 2001 16:10:17 -0700 (MST) From: Terry Lambert Message-Id: <200104262310.QAA29635@usr05.primenet.com> Subject: Re: PATCH to make maxfiles, maxfiles per proc boot-time tunable To: current@freebsd.org Date: Thu, 26 Apr 2001 23:10:17 +0000 (GMT) Cc: terry@lambert.org X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ] The problem is that param.c is *not* included in gensetdefs scope. ] Therefore linker set entries (ie: SYSINIT etc) are not executed. TUNABLE* ] entries in param.c are simply not called or used. ] ] SYSTEM_OBJS= locore.o setdef0.o vnode_if.o ${OBJS} ioconf.o param.o config.o \ ] setdef1.o hack.So ] ... ] setdef0.c setdef1.c setdefs.h: ${OBJS} ] @gensetdefs ${OBJS} ] ] param.o is not included in ${OBJS}. I dont see how this patch can work ] as-is. Has this changed in -current? I'm running on 4.3-RELEASE (now), and it has no problems. Are you sure you aren't linking param.o into your kernel anywhere? It's the linker that does the magic, not anything else (as you know); I can assure you it's running fine on my 4.3 box. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message