Page 2 – Increasing the Processes Limit
Page 2 – Upping the Ante on Processes
Now we can create a similar file to increase the processes limit. Still in Terminal, type this command:
sudo nano /Library/LaunchDaemons/limit.maxproc.plist
Again, you’ll be in a text editor. Copy and paste this content into the file, the same way you did previously for maxfiles.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple/DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>limit.maxproc</string> <key>ProgramArguments</key> <array> <string>launchctl</string> <string>limit</string> <string>maxproc</string> <string>2048</string> <string>4096</string> </array> <key>RunAtLoad</key> <true /> <key>ServiceIPC</key> <false /> </dict> </plist>
Press Control-X to save and close the text editor, then you can type exit to leave Terminal.
Finally, reboot your Mac and check the results by issuing the commands we used earlier to check our current limits, the sysctl and ulimit lines. In my case, on a mid–2010 Mac Mini, the maximum processes increased, but not to the limits I configured. Both ulimit -a and sysctl kern.maxfilesperproc revealed a limit of 1064 processes. My assumption is that is the most my Mac can handle, but do let me know if you run into the same limitation.
Use your Mac as normally for a few hours to ensure nothing goes awry. That way, you can quickly reverse your changes by deleting the files we created and rebooting. Once you know everything is working fine, you can re-enable SIP.
Turning SIP Back On
Back to Recovery Mode we go. You need to again restart your Mac, and hold Command-R until the Apple logo appears. When Recovery Mode has loaded, open Terminal and run this command:
That will turn System Integrity Protection back on.
Keep On Cruising
You can, of course, adjust those limits to whatever you believe might be reasonable. Be cautious not to get overzealous, however. Those limitations are there to protect your operating system from rogue applications that are poorly written and might leak memory like a sieve. You don’t want to go too overboard, or you might find your system slowing to a crawl when it runs out of RAM.