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 PHP
set_color
set_color(1) fish set_color(1)
NAME
set_color - set_color - set the terminal color
set_color - set the terminal color
Synopsis
set_color [-v --version] [-h --help] [-b --background COLOR] [COLOR]
Description
Change the foreground and/or background color of the terminal. COLOR is one of black, red, green, brown, yellow, blue, magenta, purple,
cyan, white and normal.
o -b, --background Set the background color
o -c, --print-colors Prints a list of all valid color names
o -h, --help Display help message and exit
o -o, --bold Set bold or extra bright mode
o -u, --underline Set underlined mode
o -v, --version Display version and exit
Calling set_color normal will set the terminal color to whatever is the default color of the terminal.
Some terminals use the --bold escape sequence to switch to a brighter color set. On such terminals, set_color white will result in a grey
font color, while set_color --bold white will result in a white font color.
Not all terminal emulators support all these features. This is not a bug in set_color but a missing feature in the terminal emulator.
set_color uses the terminfo database to look up how to change terminal colors on whatever terminal is in use. Some systems have old and
incomplete terminfo databases, and may lack color information for terminals that support it. Download and install the latest version of
ncurses and recompile fish against it in order to fix this issue.
Version 1.23.1 Sun Jan 8 2012 set_color(1)