From owner-freebsd-questions@FreeBSD.ORG Tue Jun 15 06:27:27 2010 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C23D8106566C; Tue, 15 Jun 2010 06:27:27 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94]) by mx1.freebsd.org (Postfix) with ESMTP id 81A058FC18; Tue, 15 Jun 2010 06:27:27 +0000 (UTC) Received: from core.draftnet (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 749715C03; Tue, 15 Jun 2010 06:27:44 +0000 (UTC) From: Bruce Cran To: freebsd-questions@freebsd.org Date: Tue, 15 Jun 2010 07:27:18 +0100 User-Agent: KMail/1.13.3 (FreeBSD/9.0-CURRENT; KDE/4.4.4; amd64; ; ) References: <201006150257.o5F2vS9U024389@banyan.cs.ait.ac.th> In-Reply-To: <201006150257.o5F2vS9U024389@banyan.cs.ait.ac.th> MIME-Version: 1.0 Message-Id: <201006150727.18878.bruce@cran.org.uk> Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: Olivier Nicole , questions@freebsd.org Subject: Re: Memory limit in xz (/usr/local/bin/xz) 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, 15 Jun 2010 06:27:27 -0000 On Tuesday 15 June 2010 03:57:28 Olivier Nicole wrote: > Hi, >=20 > Since I upgraded that machine from 6.x to 7.3 I am hitting a memory > limit with xz when trying to build/upgrade several ports. >=20 > The error message looks like: >=20 > /usr/local/bin/xz: /usr/ports/distfiles//libpng-1.4.1.tar.xz: Memory > usage limit reached /usr/local/bin/xz: Limit was 46 MiB, but 65 MiB would > have been needed >=20 > Is there a config parameter to tell the make files in /usr/ports to > desactivate xz memory limit? =46rom xz(1): To prevent uncomfortable surprises caused by huge memory usage, xz = has a built-in memory usage limiter. While some operating systems prov= ide ways to limit the memory usage of processes, relying on it was= n't deemed to be flexible enough. The default limit depends on the to= tal amount of physical RAM: [...] The default limit can be overridden with --memory=3Dlimit. and ENVIRONMENT XZ_OPT A space-separated list of options is parsed from XZ_OPT bef= ore parsing the options given on the command line. Note that o= nly options are parsed from XZ_OPT; all non-options are silen= tly ignored. Parsing is done with getopt_long(3) which is used a= lso for the command line arguments. =2D-=20 Bruce Cran