From owner-freebsd-questions@FreeBSD.ORG Sat Feb 4 05:10:40 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 539E216A420 for ; Sat, 4 Feb 2006 05:10:40 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id C26AD43D72 for ; Sat, 4 Feb 2006 05:10:32 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so521663wxc for ; Fri, 03 Feb 2006 21:10:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XKGDPJR4GRV9DeiLL54msd+FG5ore2uptPWFmgnTn1xf/TTXnZcY6gTEpOieWnUBL46Wlbi4e387R8iAOQwp4SaKXSYbwMGj17c+IvbtfBlecWYFMoT3qoGPNQOd1OBXEeJjT/kln6ZoSqrFHyvrAOa4mIwycvufbw8JoToXqoM= Received: by 10.70.98.16 with SMTP id v16mr3151646wxb; Fri, 03 Feb 2006 21:10:32 -0800 (PST) Received: by 10.70.67.17 with HTTP; Fri, 3 Feb 2006 21:10:32 -0800 (PST) Message-ID: Date: Fri, 3 Feb 2006 23:10:32 -0600 From: Nikolas Britton To: Xn Nooby In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: freebsd-questions@freebsd.org Subject: Re: Why does portsdb -Uu run so long? 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: Sat, 04 Feb 2006 05:10:40 -0000 On 2/1/06, Xn Nooby wrote: > Since I've gone back to the "old foolproof way" of updating my system, I'= m > doing a "portsdb -Uu" again - which has always taken forever to run on my > various machines. Is there a way to speed it up (without replacing it), = or > has anyone looked at it to see if it needs rewriting? > > I worked at a place where a monthly mainframe job ran for 24 hours, and t= he > whole plant had to shutdown while it ran (which wasnt too big a deal sinc= e > it was on Sunday). When the job started taking 36 hours to run and the > original programmer was too busy to fix it, they brought in a consultant= to > help. He re-wrote the job so it ran in 15 minutes. The original program= mer > was fired two days later. Since then, I've always been suspicous of jobs > that run for long periods of time. It just does, after you cvsup new ports cd into /usr/ports and type make fetchindex. what way is the "old foolproof way"?