From owner-freebsd-ports@FreeBSD.ORG Mon Jul 17 17:28:41 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5540916A4DE for ; Mon, 17 Jul 2006 17:28:41 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 7941F43D46 for ; Mon, 17 Jul 2006 17:28:40 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 32720 invoked by uid 399); 17 Jul 2006 17:28:39 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 17 Jul 2006 17:28:39 -0000 Message-ID: <44BBC8CB.8090903@FreeBSD.org> Date: Mon, 17 Jul 2006 10:28:43 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: "Ricardo A. Reis" References: <44B9E086.60009@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-ports@freebsd.org" Subject: Re: New portmaster version available for testing/feedback X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 17:28:41 -0000 Ricardo A. Reis wrote: > Hi Barton, > > > More one idea for portmaster, is possible limit the number of > concurrent fetch ? [ snip ] > I use portmaster for update 138 ports and now i don't have more > bandwidth :-( heh, sorry about that. I could look into the idea of limiting the number of fetches, but it's a balancing act, since people with a lot of bandwidth would like to have more, and adding another tunable for this seems like overkill to me. The good news is that in your situation, you can alleviate some of the problem by not using portmaster -a, and instead updating one or a few ports at a time. If you do (with the new version) 'portmaster -L' it will show you what you have installed, and what updates are available. If you start your updates with the root and trunk ports (that have no, or few dependencies) then you won't be doing so many fetches at once. You can keep moving "up" the dependency "tree" a port at a time, or once you get most of the ports updated you could then use -a safely. hth, Doug -- This .signature sanitized for your protection