From owner-freebsd-questions@FreeBSD.ORG Sun Aug 17 22:21:34 2003 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 23D8437B401 for ; Sun, 17 Aug 2003 22:21:34 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-107-97.dsl.lsan03.pacbell.net [64.169.107.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 098D743F93 for ; Sun, 17 Aug 2003 22:21:33 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id C4EDF66E05; Sun, 17 Aug 2003 22:21:32 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id A0EA3A48; Sun, 17 Aug 2003 22:21:32 -0700 (PDT) Date: Sun, 17 Aug 2003 22:21:32 -0700 From: Kris Kennaway To: Ralph Dratman Message-ID: <20030818052132.GA70374@rot13.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-questions@freebsd.org Subject: Re: Fragments of kernel log text in "security run" message 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: Mon, 18 Aug 2003 05:21:34 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 17, 2003 at 10:39:49PM -0400, Ralph Dratman wrote: > Recently, though, I've been seeing small fragments of text in the=20 > "kernel log" portion of that report. This happens almost every day=20 > now. Following are a few examples. There is just one fragment per=20 > report. > --------------------------------- > kq9.net kernel log messages: > >copeid 0x4 >=20 > kq9.net kernel log messages: > >8>. I get this as well on RELENG_4...I wish I knew why. Often it causes syslogd to log it at LOG_EMERG priority (=3Dspams every logged in user with the truncated message). Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/QGJcWry0BWjoQKURAtm5AKDVPGSzxbX9P0TYjmMpzHM1aRquZgCbB1Sh 2EMUL+dcHNCZfsIxYFWbDWo= =T7HE -----END PGP SIGNATURE----- --huq684BweRXVnRxX--