| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| logchecker-3.5_manual.txt | 2019-01-23 | 7.3 kB | |
| readme-3.5.txt | 2019-01-23 | 2.1 kB | |
| logchecker_wrapper_example_3.5.sh | 2019-01-23 | 618 Bytes | |
| logchecker-3.5.pl | 2019-01-23 | 26.3 kB | |
| Totals: 4 Items | 36.2 kB | 1 |
This is a simple, lightweight log file checking utility, written in perl. Current version is 3.5, which is stable and bug free. > logchecker.pl -help Usage: logchecker.pl [options] Where options and: -D means debug mode and: -d specifies alternate db file and: -e <email-address> means send email report to recipients and: -H means ask for help and: -help means ask for help and: -i means initialise or 'ignore lines this' and: -I means ignore missing message file and: -m specifies alternate message file and: -N means only print 1st log error on stdout for use with Nagios via snmpd and: -R means do not use RE file and: -r specifies RE file and: -S means do not create or use START file and: -s specifies alternate START file and: -t specifies working directory Using the -i option tells the program to create a db-file automatically from the input log file. In this mode the input log file is assumed by the program to be completely benign. Entries are appended to the db-file, so that multiple -i runs with multiple log files can be done. The re-file must be created by hand: each line contains a single regular expression, which if it matches a line in the log file means "this line is benign". The start file is created & maintained automatically by the program, it is used to store information about the position reached in the target log file on the last run, so that subsequent runs start after this position. This is to prevent old errors in the log file getting repeatedly reported on every run. If the target log file is not specified with the -m option, then the program reads stdin. The dependency/interaction between the re-file config and the db-file config is that: if a target log file line is flagged as benign by *either* the db-file *or* the re-file, then the line is *not* reported. For a target log file line to be reported as an error, it must fail to match the db-file config *and* the re-file config. I have included bash wrapper scripts that give example usage.