From owner-freebsd-current@FreeBSD.ORG Mon Nov 24 13:56:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1401216A4CE for ; Mon, 24 Nov 2003 13:56:04 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17D4743FE0 for ; Mon, 24 Nov 2003 13:56:03 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9BE1666C55; Mon, 24 Nov 2003 13:56:02 -0800 (PST) Date: Mon, 24 Nov 2003 13:56:02 -0800 From: Kris Kennaway To: Stefan Bethke Message-ID: <20031124215602.GA22244@xor.obsecurity.org> References: <310DD19B-1EBF-11D8-8B89-000393496BE8@lassitu.de> <20031124211946.GA21432@xor.obsecurity.org> <8E91F75D-1EC8-11D8-8B89-000393496BE8@lassitu.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <8E91F75D-1EC8-11D8-8B89-000393496BE8@lassitu.de> User-Agent: Mutt/1.4.1i cc: current@FreeBSD.org cc: Kris Kennaway Subject: Re: LOR filedesc structure / Giant X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2003 21:56:04 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 24, 2003 at 10:52:54PM +0100, Stefan Bethke wrote: >=20 > Am 24.11.2003 um 22:19 schrieb Kris Kennaway: >=20 > >On Mon, Nov 24, 2003 at 09:45:51PM +0100, Stefan Bethke wrote: > >>This is with a current from around two days ago, with a kernel not=20 > >>much > >>different from GENERIC. > > > >Known problem. >=20 > I do follow -current quite closely, but none of the cvs lists. It=20 > appears that I missed some important info. What should I monitor more=20 > closely? What can I do to analyze this more closely? First checking the mailing list archives and PR database for similar problem reports is often prudent. This one has been reported for several months, and I also submitted a PR about it. Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/wn5yWry0BWjoQKURAtHlAKCBYSfE4UegXLj5G30SG7w30IDyAACg667i 4pLCH5hASoPI3S1BLeAtrps= =Kn6S -----END PGP SIGNATURE----- --huq684BweRXVnRxX--