03-23-2010
Vuze/MacOS X: Too many open files
1) How can I stop Vuze from reporting the following error: "Too many open files" ?
2) What directory do I need to be in to effectively utilize this command:
sudo bash -c 'ulimit -n 8192; sudo -u username ./azureus' ?
3) Is this the maximum number of files that I can allot to Vuze on OS X (8192)?
*Note that the first 2 questions are more important to me.
---------- Post updated 03-22-10 at 01:35 AM ---------- Previous update was 03-21-10 at 03:19 PM ----------
I notice that when I type the following command into the Terminal (in Snow Leopard): launchctl limit maxfiles 10200
that it will effectively replace the default value of 256 with the larger value of 10200. However, I still receive the "Too many open files" error and the command doesn't work beyond that value. Is there a reason for that?
---------- Post updated 03-23-10 at 12:46 AM ---------- Previous update was 03-22-10 at 01:35 AM ----------
I was able to raise kern.maxfiles to 1,000,000 but I still can't raise launchctl limit maxfiles nor ulimit -n beyond 10,200. Is there a reason for this enormous discrepancy? I'm running Snow Leopard with the latest updates.
---------- Post updated at 12:47 AM ---------- Previous update was at 12:46 AM ----------
Anyone out there?
Last edited by pludi; 03-22-2010 at 05:42 AM..
Reason: corrected title
3 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am interested in knowing if anyone out there has been using the BSD UNIX that underlies
MacOS X. Is this an "industrial strength" version of UNIX? Can I run X-Windows on such
a machine? How about TeXing, pythoning, PERLing or using other useful UNIX goodies
near and dear to my shrunken... (1 Reply)
Discussion started by: ncmathsadist
1 Replies
2. UNIX for Beginners Questions & Answers
why,just beacuse that its the bottom layer uses a small amount of bsd code? In my opinion, macos and Unix are completely different. The directories are long directory structures. For example, /application, /system, /user, /volumes, etc. are completely different from the traditional /bin/ /sbin... (5 Replies)
Discussion started by: malaizhichun
5 Replies
3. Programming
Hi Neo...
This is me too except for the attention span. As soon as I find a solution to something I let others better it.
And as for doing something different I have done some bizarre stuff on here... <wink> /Me awaits the mickey take... ;oD
OT: Here is a small snippet for a terminal window... (3 Replies)
Discussion started by: wisecracker
3 Replies
LEARN ABOUT MOJAVE
ulimit
ULIMIT(3) BSD Library Functions Manual ULIMIT(3)
NAME
ulimit -- get and set process limits
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <ulimit.h>
long
ulimit(int cmd, ...);
DESCRIPTION
The ulimit() function will get and set process limits. Currently, this is limited to the maximum file size. The cmd argument is one of the
following:
UL_GETFSIZE will return the maximum file size of the current process, in units of 512-byte blocks.
UL_SETFSIZE will attempt to set the maximum file size of the current process and its children, using the second argument (expressed as a
long).
RETURN VALUES
Upon successful completion, ulimit() returns the value requested; otherwise, the value -1 is returned and the global variable errno is set to
indicate the error.
ERRORS
The ulimit() function will fail if:
[EINVAL] The command specified was invalid.
[EPERM] The limit specified to ulimit() would have raised the maximum limit value, and the caller is not the super-user.
SEE ALSO
getrlimit(2)
STANDARDS
The ulimit() function conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The ulimit() function first appeared in FreeBSD 5.0.
BUGS
The ulimit() function provides limited precision for setting and retrieving process limits. If there is a need for greater precision than
the type long provides, the getrlimit(2) and setrlimit(2) functions should be considered.
BSD
January 4, 2003 BSD