Date: Tue, 10 Jul 2001 18:10:02 -0700 (PDT) From: Leo Bicknell <bicknell@ufp.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/18587: /etc/security: improove the dmesg diff output Message-ID: <200107110110.f6B1A2o66550@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/18587; it has been noted by GNATS.
From: Leo Bicknell <bicknell@ufp.org>
To: freebsd-gnats-submit@FreeBSD.org, ls@gambit.msk.su
Cc:
Subject: Re: bin/18587: /etc/security: improove the dmesg diff output
Date: Tue, 10 Jul 2001 21:08:31 -0400
Isn't this all unreliable anyway? Since the buffer is of fixed size
it can easily be rolled over in 24 hours by log_in_vain, icmp_bandlim,
ipfw, or a simple full file system for a while. Any way you slice
it what's really needed is a way to log all of this data into a file,
where the security script can do better post processing.
That said, doesn't:
diff -b ${LOG}/dmesg.today ${TMP} | egrep "^>" | uniq -c get you most
of the way there, and keep the order? I think most duplicates show up
in a row, not scattered about.
--
Leo Bicknell - bicknell@ufp.org
Systems Engineer - Internetworking Engineer - CCIE 3440
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107110110.f6B1A2o66550>