Bug 21346

Summary:	OPEN_MAX not defined in limits.h
Product:	[Retired] Red Hat Linux	Reporter:	Ville Syrjdld <syrjala>
Component:	glibc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED NOTABUG	QA Contact:	Aaron Brown <abrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	fweimer
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-11-26 13:09:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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).