From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 19 Aug 2002 18:47:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 19 Aug 2002 18:47:17 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:28679 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Mon, 19 Aug 2002 18:47:16 -0400 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: MAX_PID changes in 2.5.31 Date: 19 Aug 2002 15:51:00 -0700 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: <200208192236.g7JMaxS28968@vindaloo.ras.ucalgary.ca> <200208192242.g7JMgmD29241@vindaloo.ras.ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2002 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Followup to: <200208192242.g7JMgmD29241@vindaloo.ras.ucalgary.ca> By author: Richard Gooch In newsgroup: linux.dev.kernel > > Ah, OK. So if I leave /proc/sys/kernel/pid_max alone, nothing will > break. Will the default ever change, or do you plan on leaving it as > is? > It probably should change at some point. I would favour changing the default to aggressive in 2.5, to smoke out bugs, and perhaps turn it back to conservative in 2.6. In 2.7, we probably should turn on aggressive for good. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt