What is the reason that kern.maxproc is set to 532? What is the tradeoff from increasing it?
I'm looking at dealing with an error "/bsd: proc: table is full" on an OpenBSD 4.2 STABLE x86 host, with the GENERIC kernel. Guessing from the archives on this and other lists, it seems a workaround to deal with it would be to muck about with kern.maxproc The "proc: table is full" error is probably caused by a perl-based CGI script which seems to spawn many processes. It will take time to deal with that properly and a quick and dirty workaround is needed. Regards -Lars
