Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 19 Aug 2002 18:38:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 19 Aug 2002 18:38:50 -0400 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:10909 "EHLO vindaloo.ras.ucalgary.ca") by vger.kernel.org with ESMTP id ; Mon, 19 Aug 2002 18:38:47 -0400 Date: Mon, 19 Aug 2002 16:42:48 -0600 Message-Id: <200208192242.g7JMgmD29241@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Ingo Molnar Cc: Linus Torvalds , Subject: Re: MAX_PID changes in 2.5.31 In-Reply-To: References: <200208192236.g7JMaxS28968@vindaloo.ras.ucalgary.ca> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1043 Lines: 29 Ingo Molnar writes: > > On Mon, 19 Aug 2002, Richard Gooch wrote: > > > > nope. Only if they use the 16-bit PID stuff in SysV IPC semaphores > > > and message queues. > > > > In other words, "yes, unless you happen not to use SysV IPC semaphores > > or message queues in any of your binaries on your system". > > no, in other words: "yes, if you use SysV IPC semaphores/semaphores > in any of your binaries in your system, which binaries were linked > against glibc 2.1 or older, and if you have set > /proc/sys/kernel/pid_max to a value higher than 32K." 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? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/