Re: How limits are enforced (was: various maxproc limits)
Re: How limits are enforced (was: various maxproc limits)
- Subject: Re: How limits are enforced (was: various maxproc limits)
- From: Terry Lambert <email@hidden>
- Date: Thu, 29 Sep 2005 21:54:23 -0700
On Sep 29, 2005, at 6:50 PM, Jerry Jorgenson wrote:
On Thu, 29 Sep 2005 16:22:51 -0700
Terry Lambert <email@hidden> wrote:
The stock answers are "Why do you need to do that?" and "Don't do
that unless you know what you are doing or you will be sorry".
Before actually answering your questions, it's likely helpful to set
the stage for the answer. So here is the design information for the
current limit enforcement model on MacOS X.
Okay, I understood what you said. But that doesn't help me any when
I can
no longer open windows on the desktop. In my previous systems I
just upped
the number nprocs and maxprocs to somthing reasonable like 8000 and
16000
respectively, relinked the kernel and all was well. In OS X I'm
lucky to
get 40 windows open. I would expect at least to be able to open up
windows
to the X maximum of 120 or so. It's a real pain not to be able to
have to
shut one window down whenever you want to open another one. Threaded
applications don't help since there seems to be a very low limit on
those
too.
I would sure like to know how to overcome what is a major problem
for me
(without compromising the stability of the system).
Thanks,
Jerry
This is a somewhat different question; this list is not intended to
answer technical support questions, and it's not an official channel
for talking to Apple. The Apple engineers who read and/or respond to
postings to this list do so to help out the developer community on
issue having to do with software development.
That's what your original post appeared to be related to, so I
responded.
For support issues, you should file a bug report <http://
bugreporter.apple.com> instead of posting to this list.
-
That said...
As I explained in points (#3) and (#5), and in my first and second
part of my answer to your question 3:
You can up the number of processes from 100 (the default) to 532 (the
default maximum) by modifying launchd.conf. You can try setting the
number higher, but it will be clamped off at 532 by the sysctl values
(per #3).
-
This sets the value for launchd, which is then inherited by
WindowServer.
WindowServer is the process that is sent the Mach message by the task
bar to launch applications, e.g. Terminal. This is really obvious if
you launch Terminal from the task bar and then do a "ps -gaxlwww" to
see its parent process ID, and the parent process ID of WindowServer.
If the windows you are talking about are "Terminal" windows, then
there is a secondary limit that will keep you below 128, which is the
number of pty's in use in the system. The current limit on the
number of simultaneous pty's open is 128 (this is the number of
device nodes for them in /dev). The actual limit will be somewhat
smaller because of internal use of ptys.
-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden