From owner-freebsd-questions@FreeBSD.ORG Sun Mar 14 08:37:10 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 82A8416A4CE for ; Sun, 14 Mar 2004 08:37:10 -0800 (PST) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2252143D2D for ; Sun, 14 Mar 2004 08:37:10 -0800 (PST) (envelope-from baughj@discordians.net) Received: from discordians.net (alb-24-194-42-195.nycap.rr.com [24.194.42.195])i2EGb7hm007027 for ; Sun, 14 Mar 2004 11:37:07 -0500 (EST) Message-ID: <40548A39.9020607@discordians.net> Date: Sun, 14 Mar 2004 11:37:13 -0500 From: "Justin Baugh, KSC" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20040313015900.0837343D39@mx1.FreeBSD.org> In-Reply-To: <20040313015900.0837343D39@mx1.FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Pernicious problem with vfork / qmail / qmail-scanner (RESOLVED) 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: Sun, 14 Mar 2004 16:37:10 -0000 Justin Baugh wrote: > I did some testing. I wrote a small program in C to fork off a > specified number of processes and leave them there. I find that > I can run exactly 39 processes as qmaild before tcpserver begins > to barf, saying it cannot fork. So, after much testing & debugging: * The problem only happens with tcpserver * The problem is not replicable in any way under 5.2.1R * The problem happens with any service/user with tcpserver, not just qmail-smtpd/qmaild I set up a testbed on my home box with a vanilla qmail install, and I wasn't able to get it to choke up. As a workaround (until I can upgrade the other box to 5.2.1R) I am running qmail through xinetd / tcpwrappers (heresy, I know), and all is well. For reference, the box in question was at 5.1-RELEASE-p10, the vendor-supplied version. Thanks, -Justin