From owner-freebsd-current Tue Feb 21 00:20:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA11199 for current-outgoing; Tue, 21 Feb 1995 00:20:46 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id AAA11192 for ; Tue, 21 Feb 1995 00:20:21 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA10312; Tue, 21 Feb 1995 19:18:14 +1100 Date: Tue, 21 Feb 1995 19:18:14 +1100 From: Bruce Evans Message-Id: <199502210818.TAA10312@godzilla.zeta.org.au> To: davidg@Root.COM, jhs@regent.e-technik.tu-muenchen.de Subject: Re: Possible kern.maxproc fatal bug Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>As last line in my /etc/rc.local I used to have >> sysctl -w kern.maxproc=300 >>An innocent >> cd /usr/ports ; make -i >>would then always crash the system (even when compiled as normal user, >>& with everything in ports having been changed to owner jhs (thus no suid 0 >>stuff lurking in /usr/ports)). > Probably because the proc table is not dynamically sized. Basically, you >can't change maxproc - it probably should not by managed by sysctl. But it is dynamically sized. I can't see any problems that would cause a panic. Old rlimits for RLIMIT_NPROC become bogus when maxproc is changed but this probably won't cause a panic. Bruce