Dear list,
I'd like to audit the events logged by the binlogd. Specifically I want
brief descriptions of every event send to the syslog (at present I send all
syslog traffic to one node and analyze it there using swatch (8)). I think
I've already solved this in a way, by using
/usr/sbin/uerf -n -o brief | /usr/local/bin/send2syslog
wrapped in a script, where 'send2syslog' is a small Perl script that
forwards messages to the syslog on the machine in question. However,
'uerf -o brief' produces more information than I really want (at least in a
format I don't particilarly fancy), and I want to know if anyone has written
similar yet better solutions to this problem (auditing binary.errlog), using
other facilities than 'uerf' for example.
Also, is it considered neccesary to audit this log? Does not seem to be done
as a standard sys admin task, except when some sort of (serious) problem
surface.
Have a nice day. With regards,
--
Thomas Strandenaes
Computing centre
University of Tromsoe
NORWAY
Received on Tue Mar 16 1999 - 10:03:44 NZDT