From owner-freebsd-stable Mon Jan 13 23:16:31 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C60DC37B401 for ; Mon, 13 Jan 2003 23:16:29 -0800 (PST) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id E476743E4A for ; Mon, 13 Jan 2003 23:16:28 -0800 (PST) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.6/8.12.6) with ESMTP id h0E7GRJB026132; Tue, 14 Jan 2003 08:16:27 +0100 (CET) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.6/8.12.6/Submit) id h0E7GQYP026131; Tue, 14 Jan 2003 08:16:26 +0100 (CET) Date: Tue, 14 Jan 2003 08:16:26 +0100 From: Stijn Hoop To: james_mapson@museum.rain.com Cc: freebsd-stable@freebsd.org Subject: Re: Partial kernel log lines in security output Message-ID: <20030114071626.GA26087@pcwin002.win.tue.nl> References: <20030111164213.A29112@ns.museum.rain.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20030111164213.A29112@ns.museum.rain.com> User-Agent: Mutt/1.4i X-Bright-Idea: Let's abolish HTML mail! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 11, 2003 at 04:42:13PM -0800, James Long wrote: > In the security run output notifications from most nearly every machine > I monitor, I see lines in the kernel log messages section similar to: >=20 > example.com kernel log messages: > > .14.232:48342 506.29.618.239:80 in via dc0 >=20 > That's just a reconstructed example, but the pattern is that first, the= =20 > log message is not from the appropriate time frame, and has the first part > of the line clipped off. Another typical example is a 'file system full' > message which is several weeks old, and similarly omits the first part > of the log entry. >=20 > What is causing these, and how can I be rid of them? Couldn't withhold this one from you guys, fresh from the daily report: -------->8----------- pcwin002.win.tue.nl kernel log messages: > All rights reserved. =20 pcwin002.win.tue.nl login failures: -------->8----------- I thought it was funny :) But seriously, it is annoying. There really is no solution? I understand that the kernel mesg buffer has to wraparound, but why doesn't it wrap on whole lines? --Stijn --=20 "Linux has many different distributions, meaning that you can probably find one that is exactly what you want (I even found one that looked like a Unix system)." -- Mike Meyer, freebsd-questions@freebsd.org, in message <15252.28617.61423.224978@guru.mired.org> --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+I7lKY3r/tLQmfWcRAmsWAJ9QIoTTMEv0pfQzvPJ4zvfVWtiJtwCgtdG4 U4He3t06y2uCm20t/XOZln8= =em2C -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message