There are some known issues with this program. Nothing too bad, but it is good for you to know about these little quirks in case you find that LogAgent is not behaving the way you expected.
- in mondir.txt, make sure that each entry is a full path and file name. For log files that you don't know in advance the name of the file, put a fake filename with no extensions (such as 'dummy').
- in config.txt, make sure that all your path names end with a '\'
- Not really an issue, but more of an installation note, if you plan to install LogAgent manually (without the install pack). You need to install the AdvNotify and Win32 API Perl modules available at http://www.generation.net/~aminer/Perl/. However, this site now appears to be down, so you can find the perl modules at http://www.oocities.org/floydian_99/Win32-AdvNotify.tar.gz and http://www.oocities.org/floydian_99/Win32-API-0.20.zip. If you use LogAgent on a single machine, this will work fine, but if you want to deploy it on a network you need to change the DLL_PATH variable in AdvNotify.pm from "$DLLPath =$Config{installsitearch}."\\auto\\Win32\\AdvNotify\\advnotify.dll";" to "$DLLPath =$ENV{SystemRoot}."\\System32\\advnotify.dll";" before compilation, and copy the file advnotify.dll to \winnt\system32. Advnotify.pm and AdvNotify.dll are buried deep in the Perl tree, so just make a file find to locate them. This way it will be easier to deploy.
- On NT4, when you do a File, Find, there may be a delay before the Find window appears. This is caused somehow by AdvNotify, but don't know more about it.
Other issues have currently been fixed.
3. Version History
5. To install
Table of contents