[PATCH] Remove CHILD_MAX

Previous thread: New thread RDSL, post-2.6.20 kernels and amanda (tar) miss-fires by Gene Heskett on Tuesday, March 13, 2007 - 1:28 am. (14 messages)

Next thread: [PATCH 1/2] avoid OPEN_MAX in SCM_MAX_FD by Roland McGrath on Tuesday, March 13, 2007 - 1:39 am. (8 messages)
From: Roland McGrath
Date: Tuesday, March 13, 2007 - 1:42 am

The CHILD_MAX macro in limits.h should not be there.  It claims to be the
limit on processes a user can own, but its value is wrong for that.
There is no constant value, but a variable resource limit (RLIMIT_NPROC).
Nothing in the kernel uses CHILD_MAX.

The proper thing to do according to POSIX is not to define CHILD_MAX at all.
The sysconf (_SC_CHILD_MAX) implementation works by calling getrlimit.

Signed-off-by: Roland McGrath <roland@redhat.com>
---
 include/linux/limits.h |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/include/linux/limits.h b/include/linux/limits.h
index c4b4e57..2d0f941 100644  
--- a/include/linux/limits.h
+++ b/include/linux/limits.h
@@ -5,7 +5,6 @@
 
 #define NGROUPS_MAX    65536	/* supplemental group IDs are available */
 #define ARG_MAX       131072	/* # bytes of args + environ for exec() */
-#define CHILD_MAX        999    /* no limit :-) */
 #define LINK_MAX         127	/* # links a file may have */
 #define MAX_CANON        255	/* size of the canonical input queue */
 #define MAX_INPUT        255	/* size of the type-ahead buffer */
-

Previous thread: New thread RDSL, post-2.6.20 kernels and amanda (tar) miss-fires by Gene Heskett on Tuesday, March 13, 2007 - 1:28 am. (14 messages)

Next thread: [PATCH 1/2] avoid OPEN_MAX in SCM_MAX_FD by Roland McGrath on Tuesday, March 13, 2007 - 1:39 am. (8 messages)