/dev/root » Expose http://devroot.org Rants of a grumpy sysadmin living in London. Mon, 30 Apr 2012 11:45:55 +0000 en hourly 1 http://wordpress.org/?v=3.3.2 Pushing the limits of Expose http://devroot.org/2007/01/29/pushing-the-limits-of-expose/ http://devroot.org/2007/01/29/pushing-the-limits-of-expose/#comments Mon, 29 Jan 2007 06:37:55 +0000 lynxman http://devroot.org/2007/01/29/pushing-the-limits-of-expose/ After this interesting article in Digg I decided out of boredom to try this up myself, here’s the result.

expose_limits

After this I noticed that the concurrent file limit by default in Mac OS X is quite low! Only around 200 processes per user, which even if it’s more than enough for most users sometimes depending on what you do you need more ;)

Mac OS X respects the sysctl.conf kernel parameter file as most unix do, so it’s just a question of adding the following parameter there:

kern.maxproc=2048
kern.maxprocperuid=512
kern.sysv.shmmax=167772160
kern.sysv.shmmin=1
kern.sysv.shmmni=32
kern.sysv.shmseg=8
kern.sysv.shmall=65536

I noticed after raising the processes value that the shared memory values where low as well, so it’s a good option to change them all at the same time.

Of course this configuration is not really recommended for machines with less than 1Gb of RAM, so be careful!

Also you need to raise the limit on launchd, launchd is Apple replacement for initd and it manages the initial limits for users.

Just edit (or create /etc/launchd.conf) and add:

limit maxproc 1024 2048
limit maxfiles 2048 4096

]]> http://devroot.org/2007/01/29/pushing-the-limits-of-expose/feed/ 1