OPEN_MAX and CHILD_MAX
Moderator, John Quarterman
std-unix at ut-sally.UUCP
Tue Nov 12 10:06:57 AEST 1985
>From seismo!gatech!akgua!whuxlm!vilya!am Mon Nov 11 12:34:18 1985
Date: Mon, 11 Nov 85 11:40:54 est
John,
I believe that both OPEN_MAX and CHILD_MAX are useful as constants
available to the programmer to protect against running out of children
or files. Use of them in a non-controlled way will, of course, require
unnecessary re-compilations when system limits are changed. Let them be
in the standard and caveat emptor.
Maybe there should be separate limits.h files, eg hardlimits.h
for things which will never ( :-) ) change on a given system, such as
hardware limits (32-bit etc.) and a softlimits.h file which contains
current limits which change when system parameters are updated etc. This
will avoid many unnecessary recompilations when the program does not use
the softlimits.
Avi Malek (vilya!am @ATT-Bell Labs, Parsippany NJ)
---
Avi Malek @ATT Bell Labs Parsippany, NJ
Volume-Number: Volume 3, Number 14
More information about the Mod.std.unix
mailing list