From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: MAX_PID changes in 2.5.31
Date: 19 Aug 2002 15:51:00 -0700 [thread overview]
Message-ID: <ajrsok$p0m$1@cesium.transmeta.com> (raw)
In-Reply-To: 200208192242.g7JMgmD29241@vindaloo.ras.ucalgary.ca
Followup to: <200208192242.g7JMgmD29241@vindaloo.ras.ucalgary.ca>
By author: Richard Gooch <rgooch@ras.ucalgary.ca>
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
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-08-19 22:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 19:55 MAX_PID changes in 2.5.31 Ingo Molnar
2002-08-19 20:06 ` Linus Torvalds
2002-08-19 20:33 ` Ingo Molnar
2002-08-19 22:31 ` Richard Gooch
2002-08-19 22:34 ` Ingo Molnar
2002-08-19 22:36 ` Richard Gooch
2002-08-19 22:41 ` Robert Love
2002-08-19 22:44 ` Ingo Molnar
2002-08-19 22:47 ` Richard Gooch
2002-08-19 23:01 ` Ingo Molnar
2002-08-20 13:44 ` Thunder from the hill
2002-08-19 22:41 ` Ingo Molnar
2002-08-19 22:42 ` Richard Gooch
2002-08-19 22:46 ` Ingo Molnar
2002-08-19 22:51 ` H. Peter Anvin [this message]
2002-08-19 23:51 ` Alan Cox
2002-08-19 23:29 ` Alan Cox
2002-08-19 23:34 ` Ingo Molnar
2002-08-20 0:33 ` Andries Brouwer
2002-08-20 0:41 ` Alan Cox
2002-08-22 22:11 ` Andries Brouwer
2002-08-22 22:27 ` Alan Cox
2002-08-22 22:59 ` Jan Harkes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ajrsok$p0m$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox