Changes from version 2.0 beta include:
- you can specify filenames instead of simply its path, which allows for keeping track of linecount. If you only wnat to specify a logfile path without the actual filename (which is how LogAgent used to work), simply put a dummy filename with NO extensions
- keeping track of linecount allows to fix the line-drop problem previous versions encountered. If the filename is omitted, linecount is still taken care of. If lines are deleted from a file when it is being monitored, LogAgent will reset the linecount to 0 and redump the whole file.
Changes from version 1.0 include:
- the configuration is now independant of source-code (big improvement). The configuration is now handled by two files, config.txt and mondir.txt
- the programming style is procedural, so it makes it for simpler code to read
- Lots of comments in the code to make it easier to understand how the program works
- checks the config files for empty spaces, empty lines, bad characters, switch '/' to '\', ...
- can have as many output directories (local or remote) as you want (one directory path per line in mondir.txt)
- can have as many monitored directories (local) as you want, listed one directory path by line after the fourth line in config.txt
- the ability to switch on and off the logging of the IP, hostname and username (first 3 lines of config.txt)
- the ability to switch on and off the display of information on the console (the fouthr line of config.txt)
- using the SHOWCONSOLE option, you can actively keep an eye on the activity in your log files by monitoring your central log directory with LogAgent
2. History behind LogAgent
4. Known issues
Table of contents