From owner-freebsd-questions@FreeBSD.ORG Fri Dec 10 20:00:28 2004 Return-Path: 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 A7A9C16A4D0 for ; Fri, 10 Dec 2004 20:00:28 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53D0F43D31 for ; Fri, 10 Dec 2004 20:00:28 +0000 (GMT) (envelope-from joshua.lokken@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so71176wri for ; Fri, 10 Dec 2004 12:00:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Iyut40tjL5w0oMfgb0BpgqCIRSwV69HrPMcX2xd7ZSyLYrJPU2UOR9RuOBzTL8cmJuMI74pZUeKd6AZ/icC/bUhxErQnh4Z0wO5dRLGyXAhGMPvSu69DGCfB2mVVai/XekTNrE6ans5KU2U6XsCR9dIwyLvFxH4BmeW3EOEFDhg= Received: by 10.54.47.62 with SMTP id u62mr203451wru; Fri, 10 Dec 2004 12:00:27 -0800 (PST) Received: by 10.54.11.34 with HTTP; Fri, 10 Dec 2004 12:00:27 -0800 (PST) Message-ID: Date: Fri, 10 Dec 2004 14:00:27 -0600 From: Joshua Lokken To: freebsd-questions@freebsd.org In-Reply-To: <20041210135721.GA96968@Klabautermann.ks.se> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041210135721.GA96968@Klabautermann.ks.se> Subject: Re: cache-update (portindex) - hangs(?) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joshua Lokken List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 20:00:28 -0000 On Fri, 10 Dec 2004 14:57:21 +0100, Christopher Illies wrote: > Hi, > > I am trying to figure out the correct way to use > sysutils/p5-FreeBSD-Portindex. From how I understand > it, the procedure for > updating the ports system would be: > > to initialise cache, afterwards occasionally : > # cache-init > [snip] > > The problem I have is now that cache-init seems to >hang: It took a couple of hours for cache-init to complete on my K-6/2 450 / 128MB machine at home. You may just want to give it some time. -- Joshua Lokken Open Source Advocate