From owner-freebsd-stable Sun Jan 21 8:11:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 976D737B401 for ; Sun, 21 Jan 2001 08:11:04 -0800 (PST) Received: from shootthemlater.demon.co.uk ([194.222.93.84] helo=cerebus.parse.net) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 14KN54-000OAz-0X for stable@freebsd.org; Sun, 21 Jan 2001 16:11:02 +0000 Received: from wbra0013.cognos.com ([10.0.0.3] helo=acm.org) by cerebus.parse.net with esmtp (Exim 3.16 #1) id 14KN4f-000Oea-00 for stable@freebsd.org; Sun, 21 Jan 2001 16:10:37 +0000 Message-ID: <3A6B09E2.EA269488@acm.org> Date: Sun, 21 Jan 2001 16:10:10 +0000 From: David Goddard X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: dmesg/security check output wierdness Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've recently noticed some odd entries in my security check output mail from a couple of 4.2-STABLE machines, so I did some digging. The following is one example: [Date: Sun, 21 Jan 2001 03:18:15 +0000] cassium.mydomain.com kernel log messages: > 06 cleared. On one machine (buildworld on 2001-01-18, not rebooted since then) I see: dmg@cassium% ls -la /var/log/dmesg.* -rw-r----- 1 root wheel 12 Jan 21 03:18 /var/log/dmesg.today -rw-r----- 1 root wheel 42 Jan 20 03:13 /var/log/dmesg.yesterday dmg@cassium% dmg@cassium% cat /var/log/dmesg.today 06 cleared. dmg@cassium% dmg@cassium% dmesg dmg@cassium% dmg@cassium% cat /var/log/dmesg.yesterday <118> setup xl0: promiscuous mode enabled dmg@cassium% The 06 cleared bit looks like it is a corruption of an entry that I usually see in /var/log/messages and /var/log/security: Jan 21 13:59:08 cassium /kernel: ipfw: Entry 306 cleared. (I use ipfw for traffic counting) The <118> setup line does not seem to be in /var/log/messages or anywhere else I looked. On another machine (buildworld on 2001-01-14, also not rebooted since then), I get similarly odd content: root@cerebus% ls -la /var/log/dmesg.* -rw-r----- 1 root wheel 1454 Jan 21 03:10 /var/log/dmesg.today -rw-r----- 1 root wheel 3470 Jan 14 03:09 /var/log/dmesg.yesterday root@cerebus% root@cerebus% dmesg scuous mode enabled root@cerebus% root@cerebus% head /var/log/dmesg.today 4 on atapci0 [normal entries snipped] root@cerebus% root@cerebus% grep scuous /var/log/dmesg.today tun0: promiscuous mode enabled ed0: promiscuous mode enabled root@cerebus% root@cerebus% grep scuous /var/log/dmesg.yesterday tun0: promiscuous mode enabled ed0: promiscuous mode enabled root@cerebus% root@cerebus% grep src /etc/security # $FreeBSD: src/etc/security,v 1.36.2.7 2000/10/30 10:40:11 obrien Exp $ Neither system has any old _secure* files hanging around in /var/run/. My assumption is that it is connected to the diff that goes on in /etc/security but I can't see anything obvious to me (although that isn't saying much). I'm hoping that it's not a hardware thing otherwise I have two machines to fix :-) Any ideas? Thanks, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message