Running wusage

Now that you have a wusage configuration file, you are ready to begin taking advantage of wusage.

First, note that if you are producing daily, weekly or monthly reports, you do not have to run Wusage more often than once per day, week or month. recommended that you run wusage shortly after midnight, on the first day of the new week or month if you are using weekly or monthly reports.

New in version 5.0: if you want to see information about the current day, week or month in progress, feel free to run Wusage more often than once per day, week or month. You will find that a report for the time period in progress is included in the index of reports, although this partial report is not included in historical graphs, in order to avoid inaccuracy.

VERY, VERY, VERY IMPORTANT: NEVER delete your log file data until Wusage has had a chance to produce a complete report for that time period. If you are producing weekly reports, don't delete or remove your log data for any part of that week until wusage has been run on the entire week's data at once.

To execute wusage, cd to the directory containing the program and enter the following command:

wusage -c wusage.conf    (or wusage.con under DOS)
(Important Unix note: Unix users may need to type ./wusage, not just wusage, to be sure that the program is found.) Note: here it is assumed that your configuration file has been created and has the name wusage.conf (or wusage.con under DOS).

If this is the first time you have run the program, a welcoming message will be displayed. Under normal circumstances, no output will be printed on the screen by wusage. If your log file is large, it may take some time for wusage to complete its run, especially if the DNS option has been selected. If your log already contains hostnames for most sites, or if speed is an issue, do not select the DNS option in your configuration file, or set the DNS option to fast, which looks up names that appear in your reports only but does not work with the ignoresites and domains options.

Note: if your log file is empty, wusage may indicate that no input was available. This is normal and the message will go away when your log file actually contains accesses. If you do have accesses in log file and you still get this message, your log file may not be in a format that Wusage supports.


Table of Contents Next

Copyright 1996, Boutell.Com, Inc.
wusage@boutell.com


Boutell.Com, Inc - PO Box 20837, Seattle WA, 98102, USA
Phone/Fax +1 206.325.3009