I had high hopes that OS X 10.4 would ship with a higher default maxproc. My old post on this subject still worked for 10.4 but what a pain that is, and you have to redo it after some System Update operations.

I just finished reading an article on launchd over at AFP548 and he mentions launchdctl for controlling launchd. One thing this utility allows you to do is set the resource limits for things that launchd launches. One of the things that launchd starts is WindowServer!

So, you just need to have launchd launch processes with a higher limit. If you run:

launchctl limit

right now you will see the maxproc is set to 100.

To change this you need to create /etc/launchd.conf file if it does not already exist and add the following line:

limit maxproc 512 2048

The first number is the soft limit and the second number is the hard limit. You can pick different values if you want.

I”ve seen mentioned some place that I can’t remember, that if you did an upgrade install to 10.4 your system might not be running launchd. This working depends on launchd being PID 1 and thus launching WindowServer. If init launched your WindowServer I’m afraid the old method will have to be your work around.

Categories: OS X Tips
Posted: July 9, 2005 11:15 PM | Perm Link
This is a Flickr badge showing public photos from pdm tagged with badge. Make your own badge here.
  • Recent Interesting Links
  • The requested page could not be found.

    require_once(/home/realpdm/lib/php/magpierss/rss_fetch.inc) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory