home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
-
-
-
-
-
-
- FrontDoor Log Analyzer
- Version 1.21
-
- Documentation
-
- 14 Aug 1991
-
- Copyright 1989 -1991 Mats Wallin
- All rights reserved
-
- (FidoNet 2:201/329)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 1
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- ABOUT FDLOG
-
- FrontDoor Log Analyzer is a utility program, which helps
- you extract the information that you find interesting in
- FrontDoors logfile. A lot of data is gathered and
- outputted in some files, which you easily can read and
- see what has happened in your system.
-
- FDLOG will run on (as far as I know) all computers where
- you can use FrontDoor
-
- No guarantee of any kind is included in this packege, you
- are using FDLOG at your own risk. I will not be
- responsible for anything that could happen to your system
- when using FDLOG.
-
- FDLOG may be used free of charge for anyone who is
- allowed to use the noncommercial version of FrontDoor. If
- you are not, and want to use this program, you should
- contribute ($10 suggested) to:
-
- Mats Wallin
- Forskottsvagen 11
- S-126 44 Hagersten
- Sweden
-
-
-
- REQUIREMENTS
-
- FDLOG uses FrontDoors logfile. To find it, FDLOG reads
- FD.SYS, which also has to be found. FDLOG searches for
- FD.SYS in the current directory or, if it doesn't exist
- there, in the directory pointed to by the environment
- variable FD. I suggest that you always have FD defined.
- Add this line to your AUTOEXEC.BAT, if you don't have it
- there already:
-
- SET FD=C:\FD
-
- or wherever you have FrontDoor.
-
- When FDLOG reads the logfile, it searches for four types
- of logrecords:
-
- $ Account information
- * Sent/Rcvd files
- + Brief messages
- % Requested files
-
- To use FDLOG, you should make sure all these loglevels
- are turned on.
-
-
-
-
-
-
- FDLOG.TXT Page 2
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- HOW IT WORKS
-
- You can use FDLOG in two ways, either by using switches
- and run it in batch mode, or with a simple menu, where
- you can choose what you want to do.
-
-
-
- WHAT FDLOG CAN DO FOR YOU
-
- FDLOG scans the logfile and gathers a lot of data. Some
- examples of the information you are able to get:
-
- A list of all outgoing calls to other systems, date
- and time of the connection, elapsed time, cost and
- name of the node you called.
-
- A list of all incoming calls.
-
- A list of all files that your system sent to other
- systems. This list doesn't include the mailfiles.
-
- A list of all files that your system received from
- other systems. No mailfiles are included here either
-
- A list of all files other systems have requested,
- with information if the file was sent.
-
- A version of the logfile that includes most
- information about incoming and outgoing calls, that
- you can find in FrontDoors logfile, but in a more
- compact form.
-
- A file as above with information about all calls
- since you last analyzed the logfile.
-
- Besides the information above, FDLOG saves information
- about all your calls in the last year, and you are able
- to create a file whenever you want to, with information
- about number of calls, elapsed time, number of
- transferred files, cost etc, that you have had to each
- node (per month) you've been in contact with.
-
- FDLOG will also (when you decide) move the logfile to an
- arcfile, zipfile, zoofile etc, and in this way save some
- diskspace.
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 3
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- INSTALLATION
-
- You can place FDLOG.EXE and FDLOGCFG.EXE wherever you
- want on your disk, it doesn't have to be in your
- FrontDoor directory.
-
- Before you use FDLOG for the first time, you have to run
- the configuration program FDLOGCFG. This program creates
- the FDLOG.SYS file, which contains information used by
- FDLOG. You can run FDLOGCFG as often you want, and change
- the information.
-
- Format:
-
- FDLOGCFG [-S] [?]
-
- Options:
-
- -S Create new FDLOG.SYS
-
- This option tells FDLOGCFG to create a new
- FDLOG.SYS file. Use it with care, since all
- information FDLOG gathers is stored in this
- file, and will be lost if a new one is created.
-
- ? Displays a help message.
-
- When you run FDLOGCFG, you will be asked some questions
- you have to answer. Most questions will have default
- answers, and if you are pleased with it, just press
- Enter.
-
- The first questions are the name of FDLOG's output files.
- All these files will be put in the same directory as
- FDLOG.EXE, if you don't supply a path.
-
- If there is a file you don't want FDLOG to create, leave
- the field blank, and no data will be written to this
- file.
-
- You will also be asked for the number of lines to print
- on each page in the output files.
-
- Then FDLOGCFG asks how old logfiles should be renamed.
- You have two options, date (FDyymmdd.LOG format) or
- daynumber of the year (FDddd.LOG).
-
- The next part is where you define the name of your
- archive program, and the name of the arcfile where FDLOG
- will move the logfiles. You don't have to supply an
- extension to the arcfile, since the archive program will
- append one automatically.
-
-
-
-
-
-
- FDLOG.TXT Page 4
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- The last thing that you can define, is the minimum cost
- of a phonecall. If this cost is higher than the cost
- found in the logfile, it will be used instead.
-
-
-
- OUTPUT FILES
-
- The following files will be created and written to by
- FDLOG: (Only NEW.FDL is created every time FDLOG runs,
- the other files are appended by default).
-
- FDLOG.SYS
-
- Contains information about all nodes, filenames,
- etc. This file will be located in the same
- directory as FD.SYS.
-
- LOG.FDL
-
- A concise report of all information found in the
- logfile. Incoming and outgoing calls, files
- transfered and requested, costs etc.
-
- NEW.FDL
-
- The same information as LOG.FDL contains, but
- this file is created every time FDLOG analyzes
- the logfile. Because of this, it contains
- information of everything that happened since
- you last analyzed the logfile.
-
- OUT.FDL
-
- Contains information about all your outgoing
- calls; date and time of call, elapsed time,
- cost, name and address of the called system.
-
- IN.FDL
-
- Contains information about all calls other nodes
- have made to you; date and time of call, name
- and address of the caller.
-
- SEND.FDL
-
- Contains information about all files (except
- mailfiles) that has been sent from your system;
- date and time, filename, size, name and address
- of the receiver.
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 5
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- RECEIVE.FDL
-
- Contains information about all files (except
- mailfiles) that your system has received; date
- and time, filename, size, name and address of
- the sender.
-
- REQUEST.FDL
-
- Contains information about all files that has
- been requested from your system and information
- if the file(s) was sent. Information included is
- date and time, file requested, number of sent
- files, name and address of the requesting
- system.
-
- REPORT.FDL
-
- This file is only created when you ask FDLOG to
- create a report. It will contain information
- about all systems you have called, number of
- calls, number (and size) of files that you have
- paid the transfer of, elapsed time and the cost.
- This information is divided per month.
-
- It will also contain the same information for
- all systems that have called your system, except
- the elapsed time and cost.
-
- The last part of this file is a list of all
- systems you have been in contact with, the first
- and last date of your calls, number of calls,
- total elapsed time and cost since you used FDLOG
- the first time, the first and last date of
- incoming calls from this system, and number of
- incoming calls.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 6
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- RUNNING IN BATCH-MODE
-
- To run FDLOG in batch mode, you have to supply at least
- one of the options below.
-
- Format:
-
- FDLOG [-A] [-C] [-D] [-M] [-N] [-R [from [to]]] [?]
-
- To turn a option off, end it with a hyphen (-).
-
- Options:
-
- -A Analyze the logfile.
-
- FDLOG will read and analyze the logfile, write
- information in the output files, and save
- information about all calls in FDLOG.SYS.
-
- -C Create new output files.
-
- Normally, all information FDLOG outputs are
- written at the end of each file, except the
- NEW.FDL. When you specify this option, FDLOG
- will create new output files.
-
- This option has no effect if you don't use the
- -A option.
-
- -D Delete FrontDoor's logfile.
-
- When FDLOG has done everything you asked it to
- do, it will delete the logfile.
-
- This option is also turned on if you use the -M
- option. If you don't want to delete the logfile
- when you use the -M option, make sure to have
- -D- AFTER the -M option.
-
- -M Move FrontDoor's logfile to an archive.
-
- This option moves the logfile to the archive
- file you defined with FDLOGCFG. By default it
- will first rename the logfile to FDyymmdd.LOG
- (where yymmdd is the date the logfile was
- created), then move it to the archive (by
- executing the program you defined as your
- archive program), and then delete the logfile.
- If you don't want FDLOG to rename and/or delete
- the logfile, make sure you have -N- and/or -D-
- AFTER the -M option.
-
-
-
-
-
-
-
- FDLOG.TXT Page 7
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- -N reName the logfile to FDyymmdd.LOG.
-
- This option renames FrontDoors logfile (FD.LOG)
- to FDyymmdd.LOG where yymmdd is the date when
- the logfile was created, or to FDddd.LOG where
- ddd is the daynumber of the year when the
- logfile was created. How to rename the file is
- decided in FDLOGCFG.
-
- This option is also turned on if you use the -M
- option. If you don't want to rename the logfile
- before moving it to the archive, make sure to
- have -N- AFTER the -M option.
-
- -R [from [to]]
-
- create a Report file.
-
- This option will create a report file, which
- contains information about your calls to other
- nodes, how much they have cost, as well as
- number and size of files transferred that you
- paid for. This information is divided per node
- and month.
-
- See alose OUTPUT FILES, REPORT.FDL.
-
- The 'from' and 'to' fields are the months that
- the report should start and end with. They
- should be given with the month number (e.g. 1 =
- Jan, 12 = Dec). If you don't supply them, they
- will default to last month. If you only supply
- the 'from' month, the 'to' month will default to
- the same month.
-
- See also the information about the report choice
- in the RUNNING IN MENU-MODE part. When you
- create a report from the menu, you are able to
- choose which nodes that should be a part of the
- report.
-
- ? Displays a help message.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 8
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- RUNNING IN MENU MODE
-
- When you start FDLOG without any options, the following
- menu will appear on the screen:
-
- Fdlog Options:
-
- A - (No) Analyze logfile
- C - (No) Create new output files
- D - (No) Delete logfile
- G - Give name to node
- I - Immediate analyze of logfile
- K - Kill (delete) nodes in Fdlog.Sys
- L - List all nodes in Fdlog.Sys
- M - (No) Move logfile to archive
- N - (No) reName logfile to FDyymmdd.LOG
- R - create Report file
- X - eXit
-
- Choice : X
-
- Some of the options in the menu (those who has a (No))
- are toggled every time you choose them, and they will be
- executed when you exit from FDLOG.
-
- The other options are executed immediately when you
- choose them.
-
- You can have more than one option on the choice line, and
- the options will be executed on at a time
-
- Options:
-
- A Analyze logfile
-
- This option analyzes the logfile when you exit
- FDLOG. See RUNNING IN BATCH MODE.
-
- C Create new output files
-
- This option tells FDLOG to create new output
- files when it analyzes the logfile. See RUNNING
- IN BATCH MODE.
-
- D Delete logfile
-
- This option tells FDLOG to delete the logfile.
- See RUNNING IN BATCH MODE.
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 9
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- G Give name to node
-
- Sometimes you don't like the name of a node that
- FrontDoor writes in the log, for example when
- the calling node doesn't know its own name, and
- FrontDoor writes -unlisted in the nodelist.
- (FrontDoor always uses the name the other system
- presents itself with).
-
- You will be asked for which nodes to name. When
- you have entered a nodenumber, FDLOG will
- present the node(s) whith this address and their
- current names. You can then edit the name to
- whatever you like.
-
- When FDLOG presents a nodename that already has
- been defined, the text '(defined)' is written
- after the name. This means that FDLOG will
- ignore whatever FrontDoor writes in the
- nodelist, and use this name instead in all
- reports.
-
- If you don't want the node to have a defined
- name anymore, delete the name instead of writing
- a new one. The name currently defined will be
- remembered, but the next time this nodenumber
- occurs in the logfile, the new name will be used
- instead.
-
- I Immediate analyze of logfile
-
- If you want to create a report file, or to
- delete som nodes from FDLOG.SYS, than you should
- first make sure that you have analyzed the
- logfile. This option does that immediatly,
- instead of waiting until FDLOG exits, as the A
- option does. Except from that, this option is
- the same as the A option.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 10
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- K Kill (delete) nodes in Fdlog.Sys
-
- Sometimes there will be nodes that you have been
- in contact with, that you don't want to have in
- your report-files. With this option you have the
- possibility to delete them.
-
- You will be asked for which nodes to delete.
- When you specify the node numbers, you can use
- the same format as in FrontDoor. If you leave
- the zone or net out, they will default to your
- own. You can also use the ALL keyword instead of
- a number.
-
- Before the nodes are deleted, you will be asked
- to confirm the deletion of the node. Because of
- this, you can specify to delete ALL nodes, and
- then answer yes or no when FDLOG asks if the
- node should be deleted.
-
- This option is only available in menu mode.
-
- L List all nodes in Fdlog.Sys
-
- This option outputs (to the screen) a list of
- all nodes FDLOG knows about.
-
- This option is only available in menu mode.
-
- M Move logfile to archive
-
- This option tells FDLOG to move the logfile to
- an archive. The D and N options will also be set
- to yes. See RUNNING IN BATCH MODE.
-
- N reName logfile to FDyymmdd.LOG
-
- This option tells FDLOG to rename the logfile to
- FDyymmdd.LOG (where yymmdd is the date the
- logfile was created). See RUNNING IN BATCH MODE.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 11
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- R create Report file
-
- This option creates a report file with
- information about costs etc. (See OUTPUT FILES,
- REPORT.FDL).
-
- You will be asked for which months the report
- should include. The default is last month.
-
- You also have the possibility to tell FDLOG
- which nodes that should be included in the
- report. See the K option above about how to
- specify node numbers.
-
- The possibility to define nodes that should be
- included in the report is only available in the
- menu mode.
-
- X eXit
-
- This options exits FDLOG. If any of the options
- A, C, D, M or N has been toggled to yes, they
- will be executed.
-
-
-
- Thats all folks, run and enjoy FDLOG.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 12
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- UPDATE HISTORY
-
- 1.00
-
- First release
-
- 1.10
-
- Changed FDLOG to use FrontDoor's (1.99b) new
- logformat.
-
- 1.11
-
- FDLOG now reads and understands FrontDoor's alias
- file. If a file is requested with an 'magic' name, it
- will be correctly reported in REQUEST.FDL.
-
- 1.12
-
- Some problems existed with logfiles smaller than
- 61440 bytes, corrected.
-
- It's now possible to define a nodes name, very useful
- for nodes that doesn't know their own name, and
- presents them self as -unlisted for FrontDoor.
-
- Peter Janssens became the first contributor till
- FDLOG. Thanks Peter.
-
- 1.13
-
- Fixed a small bug, making FDLOG display years as 1890
- instead of 1990.
-
- FDLOG will now skip lines with invalid date entries,
- and continue with the next line instead of aborting.
-
- FDLOG will now notice that a entry in the alias file
- is a service request, and not assume that it is an
- aliasname.
-
- 1.14
-
- If FDLOG only were supposed to rename, archive or
- delete the logfile, it forgot to close the logfile
- before trying to do so, resulting in a sharing error.
- Fixed.
-
- All screen output is now done via BIOS calls instead
- of via INT29. INT29 caused trouble with PC/MOS. It's
- also possible to 'SET VIDEO=x', where x is DOS, BIOS
- or INT29 to force FDLOG to use this kind of calls
- instead.
-
-
-
-
-
- FDLOG.TXT Page 13
-
-
-
-
- FrontDoor Log Analyzer (v1.21) / Mats Wallin 14 Aug 1991
-
-
- 1.20
-
- Support for the new logformat FrontDoor 2.0 uses.
- (1.99c logformat should work too).
-
- Some small changes in FDLOG.SYS, you have to run
- FDLOGCFG to update it, if you don't, FDLOG will
- abort.
-
- Fixed some cosmetics which happened when a nodes
- address was more then 14 characters.
-
- FDLOG doesn't display *.TIC files in RECEIVE.FDL and
- SEND.FDL anymore.
-
- FDLOG can now rename the logfile either to
- FDyymmdd.LOG (the old format), or to FDddd.LOG where
- ddd is the daynbr of the year. Use FDLOGCFG to choose
- which format FDLOG should use.
-
- If the logfile wasn't called FD.LOG, FDLOG wasn't
- able to rename it correctly.
-
- The list node function in the menu, now detects the
- screen length, and uses it correct (what a feature
- :-) ).
-
- 1.21
-
- This version REQUIRES FD 2.01 or later. It will not
- work with older versions of FD. This is because the
- changes in the log format, and the name changes of
- FD's system files.
-
- FDLOG will now only analyze log entries written by
- FD, e.g. it skips all logentries that contain a
- programname on the dashline, except the programname
- FD. This makes it possible to use FD.LOG for all
- utilities that uses FD's logformat, without any risk
- that FDLOG will use a logentry from another program,
- which could happen with earlier versions.
-
- I might have fixed a problem that some people have
- had, causing FDLOG to crash the PC. But I don't know
- for sure.
-
-
-
-
-
-
-
-
-
-
-
-
-
- FDLOG.TXT Page 14
-
-
-