From owner-freebsd-stable Fri Oct 3 08:04:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19564 for stable-outgoing; Fri, 3 Oct 1997 08:04:39 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA19552 for ; Fri, 3 Oct 1997 08:04:33 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.7/8.8.6) id KAA26050; Fri, 3 Oct 1997 10:04:13 -0500 (CDT) Message-ID: <19971003100413.33095@pmr.com> Date: Fri, 3 Oct 1997 10:04:13 -0500 From: Bob Willcox To: stable list Subject: fork errors - resource temporarily unavailable Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Every since I upgraded my system to 2.2-STABLE a couple of months ago I have been having this temporary but re-occuring problem with procmail getting EAGAIN errors when trying to fork one or more of the programs that I have specified in my .procmailrc file. I believe my limits are sufficiently high: Resource limits (current): cputime infinity secs filesize infinity kb datasize-cur 32768 kb stacksize 8192 kb coredumpsize 8192 kb memoryuse-cur 32768 kb memorylocked 10240 kb maxprocesses 512 openfiles-cur 512 as I never have more than about 150 or so processes running on my system, yet procmail (and only procmail!) intermittantly has this problem. Note that I have upgraded my system a few times since I first started seeing this problem (right now I'm running 2.2-stable as of about 5 days ago), yet the problem persists. Any help or advice will be greatly appreciated. Thanks, -- Bob Willcox Deliberation, n.: The act of examining one's bread bob@luke.pmr.com to determine which side it is buttered on. Austin, TX -- Ambrose Bierce, "The Devil's Dictionary"