Documentation

logresolve 2.0 can be used in a Unix `pipeline', but can also write directly to files. All default options can be defined in logresolve.h. It's best to work out what defaults are best for your purposes and set them up in logresolve.h and recompile. Most options can be overridden on the commandline.

Usage

logresolve [options] < input_log > output_log

Options: (from logresolve.txt, included in the archive)

Here's an atypically complicated example:
logresolve +s -dIPDB -k +l /tmp/LR.IPDB.lock -a60000 +r300

Options must all be separate, but options which take arguments (the ones with colons after them in the following list) work with or without the space between the option character and the argument. The Boolean options +s and +k can of course be negated as -s or -k. - and + are equivalent for non-Boolean options. Options are analyzed in the order in which they are given on the command line, so "+s -s" is equivalent to "-s".

 +s - sends stats to stderr (redirect stderr somewhere useful!)
 +k - keep failed lookups in DBM cache

 -a : <seconds> after which we should look something up again
 -r : <seconds> ...repeat failed lookups if they come out of the
        cache older than this amount of time.

 -i : <input file> to read; use '-' for STDIN.
 -o : <output file> to write; use '-' for STDOUT or '=' for STDERR.
 -t : <stats file> to write; '-' for STDOUT or '=' for STDERR. +s implied.
 -d : <DBM file> to use for persistent cache
 -l : <lockfile> to use to maintain exclusivity
 -c : <countfile> to *append* total bytecount to