Bug 21346 - OPEN_MAX not defined in limits.h
Summary: OPEN_MAX not defined in limits.h
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-26 13:09 UTC by Ville Syrjdld
Modified: 2016-11-24 15:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-11-26 13:09:42 UTC
Embargoed:

Attachments (Terms of Use)

Description Ville Syrjdld 2000-11-26 13:09:40 UTC 
OPEN_MAX is defined in linux/limits.h but limits.h doesn't include
linux/limits.h. Maybe limits.h should include bits/local_lim.h which
includes linux/limits.h?
Comment 1 Jakub Jelinek 2000-11-26 17:11:30 UTC 
OPEN_MAX is intentionally not defined because it is no longer
constant in Linux, it is runtime changeable.
/usr/include/bits/local_lim.h does include linux/limits.h but
undefines this for this reason.
Use sysconfig(_SC_OPEN_MAX) to query the same information.
Comment 2 Dmitry Bolkhovityanov 2001-07-30 11:49:47 UTC 
Sorry, but not defining OPEN_MAX *is* a bug -- some programs use this macro for
various purposes, and it is defined by POSIX standard.  Removing it causes
portability problems (most programs don't need so many files anyway).

Additionally, this macro is mentioned in glibc.info (at least in redhat-7.1).
Note You need to log in before you can comment on or make changes to this bug.