Douglas, One trick you could try is to set you kernel max processes high, then create a group of users that will then run your application. Assuming you can spread the work out, you could run your application under each user in the group, so that in effect you get (Nusers * userlimit) process slots available to you. It's a bit kludgy, but it might get you past your problem until you can cook up a custom kernel. I would imagine though, that there are scheduler efficiency reasons as to why apple set the limit at 100 and you may find a precipitous drop off of performance above that level. That's just my guess though -Brian T On Thursday, February 27, 2003, at 10:19 PM, Douglas Stetner wrote: So is there an apple bug report open on this? I am currently running at about 93 processes and do not look forward to having to build a new kernel to keep myself going. This needs to be tuneable in some fashion (I don't care if I need to reboot), but to have no option other than rebuilding my kernel (and from what I have seen on this list, correct me if I am wrong, I cannot even get up to date source out of the cvs repository!). If nothing else, Apple should do a build themselves with maxuproc at say 500, and provide that kernel as a download somewhere... Doug -- Douglas Stetner <dstetner@bigpond.net.au> "If we knew what it was we were doing, it would not be called research, would it?" - Albert Einstein _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored. _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.