Date: Wed, 23 Feb 2005 01:25:55 +0000 From: Jason Henson <jason@ec.rr.com> To: freebsd-questions@freebsd.org Subject: Re: portversion runs seemingly forever Message-ID: <1109121955l.93160l.0l@BARTON> In-Reply-To: <b346c27a58657e78a0d7301b2bcd23c4@thewambaughs.net> (from gunter@thewambaughs.net on Tue Feb 22 19:21:43 2005) References: <b346c27a58657e78a0d7301b2bcd23c4@thewambaughs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/22/05 19:21:43, Gunter Wambaugh wrote: > When I try > $ portversion -L =3D >=20 > it seems to run forever. >=20 > top yields > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU =20 > COMMAND > 51331 root 51 0 19276K 18852K RUN 0:09 90.60% 32.86% =20 > ruby18 >=20 > I have tried portsdb -uU && pkgdb -uv, to no avail. >=20 > bash-2.05b# uname -a > FreeBSD test.thewambaughs.net 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon =20 > Oct 27 17:51:09 GMT 2003 root@freebsd-stable.sentex.ca:/usr/obj/=20 > usr/src/sys/GENERIC i386 >=20 > Any ideas? > Does portversion use the index file? If so I thought you had to cd /=20 usr/src && make fetchindex, maybe after a cvsup. Also I seem to =20 remember using portversion -l "<" when I used to use it a while back. =20 To find the old ports. Just read the man page online, -L is a inverse limit, it excludes. So =20 if you have not cvsuped since you last upgraded that would be why you =20 get nothing. You say it seems to run forever, have you let it finish =20 or do you kill it? After you do the pkgdb -uv does it still take =20 forever to finish, or does it seem to just hang?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1109121955l.93160l.0l>