From owner-freebsd-questions Thu Jun 11 04:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20496 for freebsd-questions-outgoing; Thu, 11 Jun 1998 04:08:34 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20324 for ; Thu, 11 Jun 1998 04:08:14 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id NAA04309 for ; Thu, 11 Jun 1998 13:15:32 +0200 (SAT) Received: by citadel via recvmail id 4306; Thu Jun 11 13:15:09 1998 From: Graham Wheeler Message-Id: <199806111114.NAA21765@cdsec.com> Subject: Why is kern.maxproc now read-only? To: freebsd-questions@FreeBSD.ORG Date: Thu, 11 Jun 1998 13:14:10 +0200 (SAT) Cc: gram@gram.cdsec.com (Graham Wheeler) X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all I notice that kern.maxproc is readonly in 2.2.6, while it was read-write in 2.2.2. Is there a good reason for this, and will I break the kernel if I change it back to read-write? If it can't be made read-write, is there some other way of changing the upper limit? TIA Graham -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message