Thanks Quanah.

I am using Mac OS X 10.4.11 for my Postfix and Courier-Auth server.

I'm often running out of resources, despite changing things based on many google searches!

I do not have either of the files you mention. Should I simply create them?

Thanks,

James.

On 10/08/2008, at 4:54 AM, Quanah Gibson-Mount wrote:

--On Saturday, August 09, 2008 8:27 AM -0400 Wietse Venema <[EMAIL PROTECTED] > wrote:


To help other people who run into this same system-specific gotcha,
would you share the solution with the mailing list? I really can't
explore the gory kernel details of every system myself.

Certainly! :)

I bumped both the number of total processes allowed to 2048 (OSX hard limit is 2500 (???)) and the number of per-user processes also to 2048. People may not want to use the same numbers.

build09:~ build$ cat /etc/sysctl.conf
kern.maxproc=2048
kern.maxprocperuid=2048

Then you also have to set the following in /etc/launchd.conf so that the root user after boot will have the right process limit (2048). Otherwise you have to always run ulimit -u 2048 as root, then start a user shell, and then start processes for things to take effect.

build09:~ build$ cat /etc/launchd.conf
limit maxproc 2048


Once these are in place, reboot the system. After that, the limits will stay in place. You can't simply use sysctl -w because of the / etc/launchd.conf bit (slightly annoying).

These instructions work for OSX 10.4 and OSX 10.5, they may not work for any prior OSX release.

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to