lkml.org 
[lkml]   [1999]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: NR_OPEN vs OPEN_MAX vs RLIMIT_NOFILE, and a glibc bug?
Date
From
> Both getdtablesize and RLIMIT_NOFILE are only relevant for newly opened
> descriptors. See f.ex. the manual page on SunOS4:
>
> The call getdtablesize() returns the current value of the
> soft limit component of the RLIMIT_NOFILE resource limit.
> This resource limit governs the maximum value allowable as
> the index of a newly created descriptor.

This implies that the common usage of getdtablesize() to find out the
highest numbered fd is wrong to begin with, since a process could open
(or inherit!) a fd and subsequently lower RLIMIT_NOFILE. It also
suggests it is not possible to find out the highest numbered fd at
all. (And using the _soft_ limit makes it sounds yet more questionable
IMHO.)

Net result: apart from using /proc (which is Linux-specific) there is
no reliable way to close all open fds and the traditional way using
the loop like in ciped is bogus. Right?

Olaf


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [W:0.045 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site