From owner-freebsd-questions@FreeBSD.ORG Thu Mar 11 20:34:47 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 3D57016A4CE for ; Thu, 11 Mar 2004 20:34:47 -0800 (PST) Received: from mygirlfriday.info (user204.net795.mo.sprint-hsd.net [65.41.216.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id A141B43D53 for ; Thu, 11 Mar 2004 20:34:46 -0800 (PST) (envelope-from gv-list-freebsdquestions@mygirlfriday.info) Received: (qmail 13667 invoked from network); 12 Mar 2004 04:34:46 -0000 Received: from localhost (127.0.0.1) by major.mygirlfriday.info with DES-CBC3-SHA encrypted SMTP; 12 Mar 2004 04:34:46 -0000 Date: Thu, 11 Mar 2004 22:34:46 -0600 From: Gary To: freebsd-questions@freebsd.org Message-ID: <2190000.1079066086@[192.168.0.5]> In-Reply-To: <40512A99.3050508@discordians.net> References: <40512A99.3050508@discordians.net> X-Mailer: Mulberry/3.1.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Pernicious problem with vfork / qmail / qmail-scanner X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2004 04:34:47 -0000 Hi KSC, --On Thursday, March 11, 2004 10:12:25 PM -0500 "Justin Baugh, KSC" wrote: > Using truss, I see that the processes are just sitting there doing > vfork/nanosleep over and over and over, in a "Resource temporarily > unavailable" loop. Once the processes get into this state, they don't get > out of it, and it seems to build up over time (??) - i.e. more and more > forking errors until everything is hosed. The only way to fix it is to > kill off all the qmail-scanner processes. Something that just came to mind.. are you using one of the later versions of qmail-scanner and perl? Also,perhaps try reconfiguring qmail-scanner without adding in KAV for awhile, see if that narrows it down as a cause to what you are seeing under truss. -- Gary