From owner-freebsd-questions Wed Jul 31 09:51:01 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10130 for questions-outgoing; Wed, 31 Jul 1996 09:51:01 -0700 (PDT) Received: from relay1.sw.ru (myth.sw.ru [194.190.197.129]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA10116 for ; Wed, 31 Jul 1996 09:50:44 -0700 (PDT) Received: from zeus by relay1.sw.ru (8.6.12/8.6.12/jt) with SMTP id UAA16141; Wed, 31 Jul 1996 20:48:25 +0400 Message-Id: <2.2.32.19960731165420.007dcc38@myth.sw.ru> X-Sender: jt@myth.sw.ru X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 31 Jul 1996 20:54:20 +0400 To: dg@root.com From: Juri Tsibrovski Subject: Re: Considering FreeBSD Cc: questions@FreeBSD.ORG Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 09:16 31.07.96 -0700, David Greenman wrote: > No magic. It's just a value that seemed reasoonable at the time. Some >systems may create daemons with PIDs >48, so perhaps the value should be >increased a bit. YMMV. > >>So, what's the Pros et Contra, besides the risc of system crash when one of >>that processes going crazy? Any other solution? > > The worst that will happen is that the system will hang due to virtual >memory exhaustion. You should not increase it to >99, however, as 100 is >the starting point after it wraps at 30000 and thus may protect processes >that shouldn't be protected. What can prevent me from increasing that number too? I already run modified kernel with pids protected <250, and changed to 300 wrapping point. > The whole thing is admittedly somewhat of a kludge, but it actually handles >about 98% of the failure cases and is a far better solution (killing off the >process that faults when VM is exhausted) than hanging or crashing the system. In some cases (exactly what happened with me) I'd elect system crash with restart rather than have all our modem pool unusable till morning :) --- jt -- just typist :)