home *** CD-ROM | disk | FTP | other *** search
- ▌█ ▌█▀▀█ ▌█▀▀▀▀ ▌█▀▀▀▀▀█▀▀ ▌█▀▀█ ▀▀█▀▀
- ▌█ ▌█ ▌█ ▌█ ▄▄▄ ▌█▄▄ ▌█ ▌█ ▌█ ▌█
- ▌█ ▌█ ▌█ ▌█ ▌█ ▌█ ▌█ ▌█▄▄█ ▌█
- ▌█ ▌█▄▄█ ▌█▄▄▄█▄▄▄▄█ ▌█ ▌█ ▌█ ▌█
- ▌█▄▄▄ ─« RemoteAccess Log Analyzer »─
- ─« Copyright (c) 1993 by Jason Duke and Genesis Software »─
-
- ─»> Documentation <«─
-
- » WHAT IT IS «
- LogStat is a RemoteAccess utility which reads your log file and
- tallies up the occurrences of various log entries. You have the
- ability to turn the different tallies on or off via the LogStat
- configuration file.
-
- » HOW IT WORKS «
- LogStat is VERY simple. First you must create a configuration
- file. The sample configuration file included in the LogStat ar-
- chive will work fine. It is the file LOGSTAT.CFG and is ready
- to use. You may wish to alter some of the fields in thie file
- to customize your LogStat analysis. For more information on how
- to do this consult the sample configuration file. The command-
- line usage of LogStat is as follows:
-
- LOGSTAT.EXE <configfile> <logfile1> [<logfile2> <logfile3> ...]
-
- A minimum of TWO command-line parameters is required. You must
- specify a configuration file and at least one logfile (maximum
- 255 logfiles) in order for LogStat to run. LogStat will create
- standard ANSI and ASCII output files. The names and paths of
- these files can be configured in the configuration file.
-
- » ERROR CODES «
- LogStat will exit with one of four errorlevels.
- ERRORLEVEL MEANING
- 0 LogStat encountered no errors.
- 1 Not enough command-line parameters.
- 2 Specified configuration file does not exist.
- 3 Error in specified configuration file.
- If you can't get LogStat to work, verify that
- 1) You have specified all the correct filenames with exten-
- sions (and paths not in current directory).
- 2) You have edited the sample configuration file to fit your
- needs WITHOUT removing any lines!
- 3) All the data in your configuration file fits (no numbers
- where letters should be or vice versa).
- 4) You have left the first two lines of the sample configur-
- ation file UNEDITED if you are still UNREGISTERED!
-
- If you encounter a runtime error or one of the above dos error-
- levels and you think that everything is set up properly, please
- contact the author via netmail or call one of the support BBSes
- listed below.
-
- » REGISTRATION «
- LogStat is provided to you free of charge, but the author would
- REALLY appreciate your kind donations to our worthy cause. This
- program is not crippled (except for a short pause to "encourage
- registration"). To obtain a registration key and have your BBS
- name and Sysop name printed at the top of the LogStat bulletin,
- fill out the included registration form and send it in with the
- $3.00 (US currency) to Genesis Software
- 6511 Pino Real Dr.
- El Paso, TX (USA) 79912-2927
- Checks/money orders should be made out to Jason Duke. Neither
- the author nor distributors of LogStat can be held responsible
- for lost registration forms and/or money. You will receive your
- LogStat registration code within 3-4 weeks. Once you've regis-
- tered, you will be registered to ALL future versions of LogStat
- RemoteAccess Log Analyzer. If, for some reason, you change the
- name of your BBS after registering LogStat, don't worry! Just
- send us a note (Fido Netmail, CircuitNet, or regular postage)
- that you have changed along with the regular registration form,
- and, if we have your registration in our records, we will send
- you a new registration key with the new BBS name. No problem!!
-
- » SUPPORT SITES «
-
- BBS: Genesis
- Sysop: Jason Duke
- Fido: 1:381/102
- Location: El Paso, TX, USA
- Phone: 915-581-5454 (300-9600 v.32/v.42bis)
-
- BBS: Visionaire BBS
- Sysop: Curtiss Denson
- Fido: 1:381/84
- Location: El Paso, TX, USA
- Phone: 915-822-2522 (1200-14,000 v.32bis/v.42bis)
-
-