From owner-freebsd-questions@FreeBSD.ORG Tue Jun 22 11:10:44 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD42816A4CE for ; Tue, 22 Jun 2004 11:10:44 +0000 (GMT) Received: from lorna.circlesquared.com (host217-45-219-83.in-addr.btopenworld.com [217.45.219.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id E59A143D64 for ; Tue, 22 Jun 2004 11:10:39 +0000 (GMT) (envelope-from peter@circlesquared.com) Received: from circlesquared.com (localhost.circlesquared.com [127.0.0.1]) i5MBAYYn007758; Tue, 22 Jun 2004 12:10:35 +0100 (BST) (envelope-from peter@circlesquared.com) Message-ID: <40D813AA.1060802@circlesquared.com> Date: Tue, 22 Jun 2004 12:10:34 +0100 From: Peter Risdon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040611 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander References: <40D741FE.2020500@circlesquared.com> <1369091154.20040622054421@perespim.net> In-Reply-To: <1369091154.20040622054421@perespim.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: maxproc limit reached with trivial exec() in cgi script X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 11:10:45 -0000 Hi Alexander, Alexander wrote: > Hello Peter, > > Try tunning maxusers in your kernel configuration file > maxproc = 20 + 16 * maxusers > Thanks for this. Since posting my first message, I have been investigating the problem further. The server on which this behaviour appears also has mod_php installed. Running the same script using mod_php does not replicate the problem. It only occurs with cgi/suexec. This makes me suspect it is not a problem of basic system settings. It also gives me an avenue for workarounds. I notice that there was an issue with apache suexec failing to observe maxproc settings and that this was fixed fairly recently through a patch which has been included in the port.I wonder whether this patch might be at the root of the problem. I think I need to try some tests on other builds and perhaps with Linux as a control to see whether I can replicate the same behaviour. Peter.