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 CENTOS
ulimit
ULIMIT(3) Linux Programmer's Manual ULIMIT(3)
NAME
ulimit - get and set user limits
SYNOPSIS
#include <ulimit.h>
long ulimit(int cmd, long newlimit);
DESCRIPTION
Warning: This routine is obsolete. Use getrlimit(2), setrlimit(2), and sysconf(3) instead. For the shell command ulimit(), see bash(1).
The ulimit() call will get or set some limit for the calling process. The cmd argument can have one of the following values.
UL_GETFSIZE
Return the limit on the size of a file, in units of 512 bytes.
UL_SETFSIZE
Set the limit on the size of a file.
3 (Not implemented for Linux.) Return the maximum possible address of the data segment.
4 (Implemented but no symbolic constant provided.) Return the maximum number of files that the calling process can open.
RETURN VALUE
On success, ulimit() returns a nonnegative value. On error, -1 is returned, and errno is set appropriately.
ERRORS
EPERM A unprivileged process tried to increase a limit.
CONFORMING TO
SVr4, POSIX.1-2001. POSIX.1-2008 marks ulimit() as obsolete.
SEE ALSO
bash(1), getrlimit(2), setrlimit(2), sysconf(3)
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-08-06 ULIMIT(3)