Re: Reading too many Files into Array returns Nil
Re: Reading too many Files into Array returns Nil
- Subject: Re: Reading too many Files into Array returns Nil
- From: Alexander Repty <email@hidden>
- Date: Tue, 13 Sep 2005 08:29:53 +0200
Hello,
John Stiles wrote:
- use setrlimit to raise the limit to the maximum open file limit
(there appears to be no downside to this, so I don't know why it
isn't the default)
In every non-trivial program I've worked on for OS X, I've always
needed the setrlimit code eventually. There's always /something/
that ends up blowing the limit.
most Unix systems employ a way to limit open files per process or in
total, and while Mac OS X does not have a total limit on open files
per default,
zoidberg:~ arepty$ ulimit
unlimited
it does have standard limits on the various options per process, such
as the number of files or filesize. The appropriate manual page is at:
http://developer.apple.com/documentation/Darwin/Reference/ManPages/
man2/setrlimit.2.html
These limit are, as the manpage says, a way to "control maximum
system resource consumption" so that for example a runaway user
process may not hog an infinite amount of system resources. So, your
best bet is to free unused file handles, if that for some reason does
not work out for you, get the current limit (getrlimit) and set a
higher limit (setrlimit). Just setting the maximum number might cause
the system the app is run on to become unusable in case of, for
example, a huge loop or bad options supplied by the user. In that
case, the process would have to be killed to make the system usable
again.
Cheers,
Alexander
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden