From owner-freebsd-questions@FreeBSD.ORG Sun Mar 14 11:23:11 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 E676816A4CE for ; Sun, 14 Mar 2004 11:23:11 -0800 (PST) Received: from ms-smtp-03.nyroc.rr.com (ms-smtp-03.nyroc.rr.com [24.24.2.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BA4E43D1F for ; Sun, 14 Mar 2004 11:23:11 -0800 (PST) (envelope-from baughj@discordians.net) Received: from discordians.net (alb-24-194-42-195.nycap.rr.com [24.194.42.195])i2EJN8Xg013785 for ; Sun, 14 Mar 2004 14:23:09 -0500 (EST) Message-ID: <4054B122.1030406@discordians.net> Date: Sun, 14 Mar 2004 14:23:14 -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> <40548A39.9020607@discordians.net> <2090000.1079283585@[192.168.0.5]> In-Reply-To: <2090000.1079283585@[192.168.0.5]> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: 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 19:23:12 -0000 > Happen to catch this, this morning... Good dig on this.. > > Tcpserver *defaults* to a maximum of 40 simultaneous connections, so > this could very well be where your problem is.. Sorry, should have > thought of this earlier. > > You can raise this limit with the -c n (n=number) option.. > > Please see > > Nope, I'm aware of that limit, and -c was set to 120. The problem would arise with any number for n...no matter what, it would still get caught up at 40 connections. The fact that I couldn't replicate the problem with the exact same setup under 5.2.1R makes me think it's something related to the version that came with the machine. Thanks, -Justin