Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ut-sally.UUCP
Path: utzoo!watmath!clyde!cbosgd!ucbvax!ucdavis!lll-crg!mordor!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Re: OPEN_MAX and CHILD_MAX
Message-ID: <3453@ut-sally.UUCP>
Date: Mon, 11-Nov-85 19:06:57 EST
Article-I.D.: ut-sally.3453
Posted: Mon Nov 11 19:06:57 1985
Date-Received: Wed, 13-Nov-85 07:18:14 EST
References: <3428@ut-sally.UUCP>
Organization: IEEE/P1003 Portable Operating System Environment Committee
Lines: 20
Approved: jsq@ut-sally.UUCP

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