Sender: nate AT cartsys DOT com
Message-ID: <36B6861A.64E0C306@cartsys.com>
Date: Mon, 01 Feb 1999 20:59:06 -0800
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.0.36 i586)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Clarification of some errno values.
References: <3 DOT 0 DOT 6 DOT 32 DOT 19990201215716 DOT 008b0840 AT pop DOT netaddress DOT com> <199902020334 DOT WAA06724 AT envy DOT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

DJ Delorie wrote:

> >    ENFILE     'Too many open files in system'
> >                                          -- How is this distinct
> >                                             from EMFILE?
> 
> EMFILE means that a single actual file (inode) has too may directory
> entries (links) that refer to it.  Look up "ln" (the non-symbolic
> link) on any unix system.  DJGPP doesn't have this problem.
> 
> ENFILE means you called open() too many times.

I don't think this is correct.  On my Linux box, EMFILE means your
process has too many files open, while ENFILE means there are too many
open on the entire system.  I wrote a little program which does `open' a
lot.  It fails with EMFILE, but when run concurrently several times, one
fails with ENFILE.

Does DOS have per-process file limits?  I'm not sure, offhand.

Are you possibly confusing it with EMLINK?
-- 

Nate Eldredge
nate AT cartsys DOT com