Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=77293034696e3e0b6c8b8fc1f96be091104b3d2b
Commit:     77293034696e3e0b6c8b8fc1f96be091104b3d2b
Parent:     c09edd6eba683741bb8aa8e388a2bfaf1c1a28f9
Author:     Roland McGrath <[EMAIL PROTECTED]>
AuthorDate: Tue Jul 17 04:03:49 2007 -0700
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Tue Jul 17 10:23:03 2007 -0700

    Remove OPEN_MAX
    
    The OPEN_MAX macro in limits.h should not be there.  It claims to be the
    limit on file descriptors in a process, but its value is wrong for that.
    There is no constant value, but a variable resource limit (RLIMIT_NOFILE).
    Nothing in the kernel uses OPEN_MAX except things that are wrong to do so.
    I've submitted other patches to remove those uses.
    
    The proper thing to do according to POSIX is not to define OPEN_MAX at all.
    The sysconf (_SC_OPEN_MAX) implementation works by calling getrlimit.
    
    Signed-off-by: Roland McGrath <[EMAIL PROTECTED]>
    Cc: "David S. Miller" <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
---
 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 eaf2e09..c4b4e57 100644
--- a/include/linux/limits.h
+++ b/include/linux/limits.h
@@ -6,7 +6,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 OPEN_MAX         256   /* # open files a process may have */
 #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 */
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to