Date: Fri, 3 Sep 2004 21:49:14 -0400 From: Mike Hauber <m.hauber@mchsi.com> To: freebsd-questions@freebsd.org Subject: portupgrade, portsdb -U failing, ruby dumping core Message-ID: <200409032149.14573.m.hauber@mchsi.com>
next in thread | raw e-mail | index | archive | help
I've seen this twice on my system (4.1.0). The first time it happened, I fetched a new index, ran cvsup, updated the portsdb, and everything seemed to work okay for about three weeks. The second time was a couple of days ago. I rebuilt a cvsup'd system, removed the entire ports tree, reinstalled it, ran cvsup, and portsdb updated without incident. So far, no problems, and I've been poking at it regularly just to see if it will do it again soon so I can try to capture it. At first, I figured it had something to do with blanktime (or apm), but I didn't have them installed the second time it happened... Still waiting to see if I can catch it in the act. That said, I don't think it has anything to do with the version of the system's build. More later (hopefully not, but... :) ) Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409032149.14573.m.hauber>