From owner-freebsd-questions@FreeBSD.ORG Tue Apr 18 13:45:46 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 F135316A42B for ; Tue, 18 Apr 2006 13:45:46 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FB1B43D49 for ; Tue, 18 Apr 2006 13:45:45 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 19391 invoked from network); 18 Apr 2006 13:45:44 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 18 Apr 2006 13:45:44 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 159B028423; Tue, 18 Apr 2006 09:45:44 -0400 (EDT) Sender: lowell@be-well.ilk.org To: "Roger Williams" References: From: Lowell Gilbert Date: 18 Apr 2006 09:45:44 -0400 In-Reply-To: Message-ID: <44vet79euv.fsf@be-well.ilk.org> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Out of memory during ridiculously large request X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 13:45:47 -0000 "Roger Williams" writes: > Since an upgrade to 6.0 (perl 5.8.8) I am getting the following error: > > >>Out of memory during ridiculously large request at > /usr/local/pop-before-smtp-1.36/pop-before-smtp line 355 > > Below is the offending line: > > >> foreach (keys %db) > > While googling I see there are other programs having the same issue. Any > ideas on how to get perl/freebsd to let the program work? Did you do the perl-after-upgrade step, as the upgrade instructions suggested? It sure looks like one of your perl ports hasn't been updated appropriately; you could always rebuild all of them to be sure.