Subject: Re: Time to bump the default open files limit?
To: Christos Zoulas <christos@zoulas.com>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
List: tech-kern
Date: 06/20/2002 14:42:55
In message <Gy0xDu.6II@tac.nyc.ny.us>Christos Zoulas writes:
>I think that from the POV that most programs use very few file descriptors
>and a few programs use a lot of file descriptors, we should leave things
>as they are and make the few programs that need more descriptors bump their
>resource limits.
"me too"
>We should also fix the error handling code, so that it
>does not take hours to figure out what went wrong. It is not like rocket
>science.
It isn't obvious how to get the info so as to check for this error.
I kept running into this a year or two back, when prototyping several
some web apps (up tens of thousands of sockets simultaneously open).
I've since mainatiend a hack to procfs whichs appends the per-process
current open file count to the end of /proc/<pid>/status.
I still dont know of any better way to grab this info for an arbitrary
process.