Date: Tue, 21 Feb 1995 19:18:14 +1100 From: Bruce Evans <bde@zeta.org.au> To: davidg@Root.COM, jhs@regent.e-technik.tu-muenchen.de Cc: current@FreeBSD.org Subject: Re: Possible kern.maxproc fatal bug Message-ID: <199502210818.TAA10312@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502210818.TAA10312>