From owner-freebsd-questions@FreeBSD.ORG Tue Jan 25 15:40:43 2005 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 3D09916A4CE for ; Tue, 25 Jan 2005 15:40:43 +0000 (GMT) Received: from out014.verizon.net (out014pub.verizon.net [206.46.170.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 746B943D39 for ; Tue, 25 Jan 2005 15:40:42 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out014.verizon.net ESMTP <20050125154041.UYYA28388.out014.verizon.net@ringworm.mechee.com>; Tue, 25 Jan 2005 09:40:41 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id A05082CE74E; Tue, 25 Jan 2005 07:36:58 -0800 (PST) From: "Michael C. Shultz" To: freebsd-questions@freebsd.org Date: Tue, 25 Jan 2005 07:36:54 -0800 User-Agent: KMail/1.7.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501250736.56780.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out014.verizon.net from [4.26.84.7] at Tue, 25 Jan 2005 09:40:41 -0600 cc: Bart Silverstrim Subject: Re: portmanager loop? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 15:40:43 -0000 On Tuesday 25 January 2005 07:07 am, Bart Silverstrim wrote: > I had (have?) several packages in the ports collection that needed > updating, and recently someone in the list was talking about using > portmanager -u to save on problems with updating; it doesn't touch > the ports database, it won't mess up the collection, it walks > dependencies automagically, etc...should be as easy as "portmanager > -u" and letting it do it's magic, correct? > > On the Dell 2650 this is running on (FBSD 4.9) *seems* to keep > recompiling xfree86-4-server. Is there a way to tell if it is stuck > in a loop? I had to stop it yesterday after it had been upgrading > for several hours. Can someone take a look at this status output and > tell me if I need to do something to get a successful portmanager > run, or verify that letting it go will eventually "untangle" whatever > it's doing? The portmanager -s shows: > > # portmanager -s > --------------------------------------------------------------------- >--- ------- > PMGRrStatus 0.2.4_0 info: Creating inital data bases > --------------------------------------------------------------------- >--- ------- > awk: cmd. line:1: fatal: cannot open file > `/usr/local/etc/portmanager/pm-020.conf' for reading (No such file or > directory) You exposed a bug here, I'll look into it today. Portmanager should abort if this file is missing. What it is supposed to do is copy /usr/local/etc/portmanager/pm-020.conf.SAMPLE to /usr/local/etc/portmanager/pm-020.conf when it is missing so I will have to fix this, for now will you please do it manually? [snip] > OLD p5-Convert-TNEF-0.17 built with old dependency > p5-Mail-Tools-1.64, current dependency is p5-Mail-Tools-1.65 > OLD p5-Digest-MD5-2.33 built with old dependency p5-Digest-1.08, > current dependency is p5-Digest-1.10 > OLD mod_php3-3.0.18_4 built with old dependency apache-1.3.31_6, > current dependency is apache-1.3.33_1 > OLD tcplist-2.2_1 built with old dependency lsof-4.72.2, current > dependency is lsof-4.74 > OLD squidGuard-1.2.0_1 built with old dependency squid-2.5.7_1, > current dependency is squid-2.5.7_8 > --------------------------------------------------------------------- >--- ------- > status report finished > ===================================================================== >=== ======= After you copy /usr/local/etc/portmanager/pm-020.conf.SAMPLE to /usr/local/etc/portmanager/pm-020.conf I would like to see a couple of cycles of portmanager -u output if you don't mind. Just run assuming your shell is tcsh portmanager -u >& portmanager.log if bash then portmanager -u 2>&1 portmanager.log then monitor it with tail -f portmanager.log I just need to see where the loop occurs. I've been planning to post a patch tonight anyways and if there is something here to be fixed I'd like to include it in the patch. Thank you. -Mike