Date: Mon, 3 Mar 2003 18:20:31 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Matthias Andree <ma@dt.e-technik.uni-dortmund.de> Cc: Kris Kennaway <kris@obsecurity.org>, Doug Barton <DougB@FreeBSD.ORG>, ports@FreeBSD.ORG Subject: Re: New additions to http://bento.freebsd.org/errorlogs/ Message-ID: <20030304022031.GB80212@rot13.obsecurity.org> In-Reply-To: <m38yvvvrtg.fsf@merlin.emma.line.org> References: <20030302235403.GA33223@rot13.obsecurity.org> <20030302190352.L1326@znfgre.tberna.bet> <20030303034451.GB34415@rot13.obsecurity.org> <m38yvvvrtg.fsf@merlin.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--UHN/qo2QbUvPLonB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 04, 2003 at 02:33:31AM +0100, Matthias Andree wrote: > Kris Kennaway <kris@obsecurity.org> writes: >=20 > > Yes..they were transient build problems on those two architectures > > that will go away once another build completes and the logs recycle. > > I'm not sure much can be done about this. >=20 > Is it possible to weed out logs and corresponding indices that point to > logs which exhibit one of these errors? A somewhat more macroscopic grep > -v (or grep -l | xargs rm ; rebuild-log-indices) might do. There are n possible transient failure modes (where n -> infinity), so I don't know if this will be very productive to pursue. Kris --UHN/qo2QbUvPLonB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+ZA1vWry0BWjoQKURAgaeAJ4r3n11IEJG9CJBAbewXPQgs2v98ACguHne 7OU7HrAuJjJ2U0kPJhbomBE= =v6N4 -----END PGP SIGNATURE----- --UHN/qo2QbUvPLonB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030304022031.GB80212>