Upgrade Procedure: patchlevels within the 8.0 series are free upgrades for all registered 8.0 users. Windows users should simply download and run the latest self-extracting executable installation program. Unix users should simply
cdto the parent directory of the existing wusage8.0 directory before untarring the new distribution in order to upgrade the binaries. Be sure to
08/18/12: Wusage 8.0 P52 for Modern Linux DistributionsLinux binaries for modern 64-bit and 32-bit Linux distributions have been made available.
07/06/07: Wusage 8.0 P52 for Windows and LinuxWusage 8.0 P52 corrects an occasional problem when local file paths, such as the report directory, contain spaces. Although this is a rare situation in Unix, it is common in Windows. Windows users are strongly encouraged to install Wusage 8.0 P52. There is no upgrade fee for registered users of Wusage 8.0.
09/16/04: Wusage 8.0 P50 for WindowsWith the release of Windows XP Service Pack 2, Microsoft chose to remove support for a mechanism which Wusage relied upon in order to provide easy access to the program from the start menu. Wusage 8.0 P50 uses an alternative mechanism and is fully compatible with all modern versions of Windows. This issue does not affect non-Windows users.
09/09/04: Wusage 8.0 P49 for Many Operating SystemsWusage 8.0 P49 provides the following improvements:
- Fix for a rare problem when emitting user agent reports which caused report failure.
- The application server can now be configured to bind to a specific port and IP address via the "optimization settings" page. This change does not take effect until the service is restarted (Windows) or the wusage -wusage-check-server process is killed and allowed to restart itself at the next 5-minute mark (Unix).
05/21/04: Wusage 8.0 P47 for Many Operating SystemsWusage 8.0 P47 provides the following improvements:
- Full support for IPv6 addresses in log files, including reverse DNS lookups.
- Search keywords report improvement: Wusage now recognizes cases in which the query prefix appears in the referring URL more than once, and accepts the first non-empty instance. Several common search engines are currently passing referring URLs of this nature.
- More informative status display during the reopening of log files between the reverse DNS/structure study pass and the analysis pass.
- FTP log file fetching support will try a rooted path as a subdirectory of the user's home directory if treating it as a rooted path fails. This increases compatibility with standards, and also with various interpretations of FTP URLs actually found in the field.
- Other minor fixes.
04/21/04: Wusage 8.0 P46 for Many Operating SystemsWusage 8.0 P46 addresses the following issues:
- An issue with DNS resolution has been corrected. This issue may have caused excessive queries per second, or in some cases, an "update process failed" error.
- Sluggish report generation in 8.0 P45 has been corrected.
- A valid From: header with a full name is now included in email reports, for better compatibility with spam filters.
- As required by strict SMTP servers, email report message bodies now contain CR/LF separators rather than bare linefeeds.
- Missing title tag added to global progress display.
03/23/04: Wusage 8.0 P45 for Many Operating SystemsWusage 8.0 P45 addresses the following issues:
- A problem with out-of-range result codes in log files has been corrected.
- A "switch accounts" button has been added. Also, the name of the currently active ISP mode account is now displayed on the control page. Those operating the software in ISP mode will appreciate this convenience for their customers who have more than one virtual host.
- The "off" button has been removed. Wusage automatically times out and shuts down unnecessary sessions, and the "off" button was causing confusion and anxiety for end users.
- Makes multiple attempts to open local files, in order to address reported problems on busy Windows servers.
- Can simultaneously open as many as 400 log files, as modern versions of server operating systems permit. (Wusage can still intelligently close and reopen log files when the number exceeds 400.) This step is also expected to be helpful on Windows servers.
- On Windows, the IP address of the DNS server is now determined by parsing the output of ipconfig /all, rather than via the registry. This resolves IP address resolution problems reported by some Windows users.
- On Windows, no attempt is made to query the IIS metabase to convert W3SVC* ids to virtual domains, unless a shared local log file is actually in use. On a few systems, standard Microsoft scripts used to do so can hang indefinitely. Wusage no longer attempts this query except when running directly on an actual IIS server and with an actual shared log file for all hosts, the only time when this query is necessary.
01/29/04: Wusage 8.0 P44 for Many Operating SystemsWusage 8.0 P44 addresses the following issues:
- Windows users: Microsoft has announced plans to stop supporting basic authentication usernames and passwords embedded in the URL in Internet Explorer. When Microsoft does release this patch, logging into older patchlevels of Wusage via the Start menu will no longer be possible. Wusage 8.0 P44 addresses this issue by passing the username and password in a different way at startup time. (The username and password are then moved to a session cookie and removed from the displayed URL thereafter.)
email.emlfiles are now deleted after their purpose is served in order to save space in report directories.
- Problems with choosing "ALL" have been corrected in certain reports. It is still not advisable to display "ALL" documents or visitor sites, for instance, when this report might be too large to open; if you want to show a large number of entries, choose the largest number you can reasonably imagine reading through, such as 1000.
10/14/03: Wusage 8.0 P43 for Many Operating SystemsWusage 8.0 P43 addresses the following issues:
- Calculation of the number of unique visitors accessing the server has been much improved. In situations where user-identifying cookies are not available, unique visitor figures were unrealistically high due to the increasing popularity of rotating-IP proxy servers which mask the true number of users. Wusage now scales the total accesses from such identity-masking IPs by the average number of accesses for each IP address that is not used in a rotating fashion, rather than counting every unique IP address as a unique visitor. This model is definitely more accurate, however users who wish to retain the older model may wish to consider using the single access visits option. See our definitions page for more information.
- Console output suppressed on successful updates, as requested by Unix cron mail recipients.
- Rare situations involving days for which only errors such as "404 not found" were logged, and no successful accesses, could cause these errors to be misattributed to preceding days or prevent the generation of otherwise empty reports for such days. This problem has been corrected.
- Windows users: problems browsing network shares and writing reports to network shares have been corrected. Note: if you can't see your network shares, you probably are running the Wusage service as the local user SYSTEM and need to give SYSTEM appropriate privileges, or use the services control panel to start Wusage as an administrative user with access to your network shares.
- Windows users: report directory selector now allows network share and drive letter changes.
10/14/03: Wusage 8.0 P42 for WindowsWusage 8.0 P42 addresses certain problems with the Windows command shell in some versions of Windows, allowing Wusage 8.0 to operate correctly when the installation path of the program contains spaces. This is a strongly recommended upgrade for Windows users.
10/11/03: Wusage 8.0 P41 for Many Operating SystemsWusage 8.0 for P41 corrects an oversight at the time of release of 8.0 P40 which causes P40 to fail. This was due to the accidental failure to remove a testing mechanism that required the existence of a specific directory. We apologize for the error and have set measures in place to prevent a similar problem from occurring in the future.
10/09/03: Wusage 8.0 P40 for Many Operating SystemsWusage 8.0 P40 has been released. Wusage 8.0 P40 addresses the following issues:
- Windows users: better support for Mozilla, Netscape and Opera as well as Internet Explorer as the user's default browser when connecting to the Wusage service via the Wusage 8.0 item in the Start menu. This automatic login process now works with any browser, provided that your browser accepts session cookies (you do not have to accept long-term cookies).
- .jsp added to standard list of file extensions considered to be pages
- Empty c-dns fields found in Windows Media Server logs no longer override perfectly good c-ip fields.
- When retrieving log files, FTP login names may now include an @ sign and a domain name.
09/17/03: Wusage Hosted Statistics Service Now AvailableUsers who find it difficult or tedious to install and manage their own software can now get the benefits of Wusage without the need to install software. Check out the new Wusage Hosted Statistics Service. Of course, we are still 100% committed to offering and enhancing Wusage as a standalone software package!
07/14/03: Wusage 8.0 P39 for MacOS X Re-Packaged CorrectlyWusage 8.0 P39 was not packaged correctly for MacOS X at the time of original release. As a result, the download actually contained 8.0 P26. We have replaced this with the correct, current version. We apologize for the error. You may check your version and patchlevel with this command:
07/07/03: Wusage 8.0 P39 for Many Operating SystemsWusage 8.0 P39 has been released. Wusage 8.0 P39 addresses the following issues:
- Download percentages and document titles options are now inquired about in the "new configuration file / new account" wizard, discouraging their use on database-driven sites that do not respond well to the resulting load
- Potential loss of
servernamesoption setting when configuration is edited directly by individual ISP mode users corrected
- Handling of mismatched passwords, missing account name, illegal account name, etc. improved in ISP mode "add account" process
- "Cancel This Update" and "Cancel All" now work properly in Status window (typically recognized and acted upon by the next 5-second refresh)
- Double-clicking of files and directories now supported in file selector, as users typically expect
- Safari browser properly recognized in Top Browsers report
- Final DNS timeout reduced to 5 seconds in keeping with typical current performance expectations
- In new configurations, better recognition of new versions of Netscape and Mozilla
03/25/03: Wusage 8.0 P38 for Many Operating SystemsWusage 8.0 P38 has been released. Wusage 8.0 P38 addresses the following issues:
- Problems with the "quick query" feature have been corrected
- Scheduled updates for simple mode now work properly; this problem did not affect advanced or ISP mode
- Intermittent ISP mode problems on some operating systems, notably FreeBSD and some other Unix flavors, have been corrected
03/14/03: Wusage 8.0 P37 for Many Operating SystemsWusage 8.0 P37 has been released. Wusage 8.0 P37 addresses the following issue:
- The "referrers by document" and "referrers by document not found" reports did not always assign the right referrers to the right documents. This problem did not affect the "top referrers" and "top referring sites" reports and did not affect any search keyword reports. This problem has been fixed in Wusage 8.0 P37.
02/18/03: Wusage 8.0 P36 for Many Operating SystemsWusage 8.0 P36 has been released. Wusage 8.0 P36 addresses the following issues:
- Screen resolution figures reset properly for each day's report (accuracy in percentage terms was already OK)
- Certain URLs handled better in documents by directory and top documents report
- Resource savings when the
downloadpercentagesoptions are both turned off
01/29/03: Wusage 8.0 P35 for Many Operating SystemsWusage 8.0 P35 has been released. Wusage 8.0 P35 addresses the following issues:
- The new
allentriesoption, which defaults to ON, causes Wusage to accept all log file lines regardless of web server ID-related fields, such as the server IP address field, which often caused earlier patchlevels to reject otherwise acceptable IIS log files with no hostname field.
- 8.0 P35 and higher will properly generate the
screen resolution report when the
manyserversoption is in use; as an additional benefit, accesses to the special
wusage_screen_properties.giffile will still be recognized even if it is placed in a subdirectory.
-homecommand line option is now passed on to child processes which perform analysis for individual accounts, avoiding the need for special environment settings in Unix crontab files .
01/06/03: Wusage 8.0 P34 for Many Operating SystemsWusage 8.0 P34 has been released. Wusage 8.0 P34 addresses the following issue:
- A problem which prevented simple mode from working properly has been corrected. This problem did not affect advanced or ISP mode operation.
12/03/02: Wusage 8.0 P33 for WindowsWusage 8.0 P33 addresses a problem which prevented the Windows version of Wusage from responding properly to the OK button and certain other buttons in the configuration editor. This issue did not affect any other operating systems and was related to a build process issue; no code changes were needed.
11/27/02: Wusage 8.0 P32 for Many Operating SystemsWusage 8.0 P32 has been released. Wusage 8.0 P32 addresses the following issues:
- A new option,
on. Users who find the difference in unique visitor measurements between versions 7.x and 8.0 to be disconcerting may wish to use this option. We recommend that new users leave this option turned off.
- Newly created 8.0 P32 configurations and accounts display the top 50 pages, images, etc. Of course, this is adjustable via Edit Configuration -> Configure Reports -> Object Types. However some users never found this and assumed that no more than 10 pages could ever be shown.
- Escaped user agent strings in Roxen server logs are now parsed correctly.
- A rare problem causing extremely large console.txt files to be created during scheduled updates has been corrected
- Potential race conditions on some operating systems involving ISP mode account logins have been corrected. A related FreeBSD problem has been addressed (a new FreeBSD binary will be available soon).
10/18/02: Wusage 8.0 P31 for Many Operating SystemsWusage 8.0 P31 has been released. Wusage 8.0 P31 addresses the following issues:
- 8.0 P30 did not always close Internet sockets completely. With a large log file this could cause difficulties with the document title fetching feature and/or prevent the analysis from completing. This problem has been fixed.
- The operating system and web browser reports did not always function properly when a "pretty" label in the osgroups list (such as "Windows NT") happened to appear exactly in an actual log entry. This prevented the program from displaying the percentage of Windows 2000 and XP operating system users correctly. This problem has been fixed.
- Visits were not always registered properly to individual documents mentioned in the historical totals report (part of the executive summary, and the source of information for historical graphs). This problem did not affect accesses or bytes, only visits, and did not affect the count of overall visits to the site. Correct figures for visits were displayed in the "top documents" and "top documents by directory" reports. This problem has been fixed.
- Proper error messages are now displayed in several additional abnormal situations.
10/11/02: Wusage 8.0 P30 for Many Operating SystemsWusage 8.0 P30 has been released. Wusage 8.0 P30 addresses the following issues, the most important of which are Windows-specific:
- When accessed by Internet Explorer on the same computer that runs the service (a common configuration), Internet Explorer would often fail to display certain pages in the configuration editor, making it difficult to use. This problem did not appear in any other web browser, or on non-Windows operating systems. This problem has been fixed. This was due to a frustrating problem with the Windows Sockets layer; other windows programmers who have encountered similar "can't find server or DNS error" behavior from Internet Explorer are welcome to ask about the solution.
- When running on the same computer as IIS, Wusage can determine the web server names corresponding to W3SVCX names. However, this did not work properly when Wusage was installed at a path containing spaces. This has been fixed.
- "Out of disk space" error detection has been improved, and the writing of work-in-progress databases has been modified to ensure that an out of disk space error never causes corruption. This fix applies to non-Windows systems as well.
10/03/02: Wusage 8.0 P29 for WindowsWusage 8.0 P29 has been released. Wusage 8.0 P29 addresses the following Windows-specific issue:
- From 8.0 P24 to 8.0 P28, first-time installations of Wusage on Windows NT, 2000, and XP machines produced an error message, and the Wusage service was not successfully started. This problem has been fixed in 8.0 P29. Those who were unable to install Wusage 8.0 under Windows between September 6th, 2002 and October 3rd, 2002 are strongly encouraged to download and install 8.0 P29,
- From 8.0 P24 to 8.0 P28, first-time installations of Wusage
on Windows NT, 2000, and XP machines produced an error message,
and the Wusage service was not successfully started. This problem
has been fixed in 8.0 P29. Those who were unable to install Wusage
8.0 under Windows between September 6th, 2002 and October
3rd, 2002 are strongly encouraged to download and install 8.0 P29,
which has been verified to work properly in first-time installations
on systems that have not run Wusage before.
10/02/02: Wusage 8.0 P28 for Many operating SystemsWusage 8.0 P28 has been released. Wusage 8.0 P28 addresses the following issues:
- Wusage 8.0 P28 and above keep temporary files in a new, better location. This change improves Windows performance, avoids out of virtual memory errors in Solaris, and also avoids permissions problems in Windows NT, 2000 and XP. For more information, see details below.
cancelbutton now works during the "waiting 60 seconds for DNS to complete" stage.
- Status files no longer accumulate in large numbers
wusage-statusfolder, which is automatically swept clean of stale files on a regular basis in 8.0 P28.
- The -p option, used to change the port that Wusage responds on, is now propagated to future restarts of the program carried out by cron under Unix.
wusage-tmp, within the
datafolder, which is found in the folder where Wusage is installed. The Unix version keeps temporary files in a directory called
.wusage-tmp, within the home directory of the Unix user that Wusage is running as. If needed, the temporary file directory can be changed by setting the new
WUSAGE_TMPenvironment variable before launching the program. Wusage 8.0 P28 and above will not look at the
TMP, TEMP, TMPDIR, and TEMPDIRvariables, because they are so frequently set to locations where large amounts of data should not be stored even temporarily.
09/22/02: Wusage 8.0 P27 for Windows
- Windows NT/2000/XP users: some users have reported problems installing Wusage when the installation path includes spaces. This has been traced to a problem when installing our Windows NT service. This problem has been corrected. If you were not able to install Wusage 8.0, especially on Windows XP, be sure to download 8.0 P27.
- The site name found in referring URLs is now converted to lower case (domain names are case insensitive). This prevents false distinctions between identical referring sites differing only in capitalization.
- Advanced mode: the "recently used configuration files" pulldown menu now operates properly in all situations.
- More than one matching rewrite rule can now be applied to the same log file line. Rules are applied in the order they appear. (This was already the case for rules based on regular expressions.)
09/18/02: Wusage 8.0 for MacOS X 10.2Wusage 8.0 is now available on MacOS X for the first time. This initial release requires familiarity with the MacOS X Unix prompt; the installation procedure is identical to that for all other Unix versions of Wusage 8.0. In the future, we also hope to offer MacOS X Wusage for those who are not comfortable with the Unix prompt.
We also continue to make Wusage 8.0 P26 available on more Unix platforms, including NetBSD 1.5 on Mac hardware.
09/14/02: Wusage 8.0 P26 for UnixPrevious patchlevels sometimes had difficulty performing automatic scheduled updates via cron when the HOME environment variable did not end with a / at the time Wusage was first run to install its crontab entries. Also, Wusage 8.0 P25 for Linux produced harmless but unwanted extra messages during hourly cron jobs. These problems have been fixed. 8.0 P26 is recommended for Unix users having trouble with scheduled updates. These issues do not affect Windows users.
We are committed to correcting any problems encountered with Wusage 8.0! Development of Wusage 9.0 is also underway.
09/09/02: Wusage 8.0 P25 for Linux Statically LinkedA few customers had difficulty with the dynamically linked release of Wusage 8.0 P25, which required that libpng be installed. To avoid such concerns, Wusage 8.0 P25 has been reissued in a statically linked form. There was no change made to the software and it functions exactly as before.
09/09/02: Wusage 8.0 P25 for LinuxWusage 8.0 P24 had difficulty providing a web interface under Linux. This problem has been corrected. This issue does not affect Windows. 8.0 P25 is a strongly recommended upgrade for Linux users of 8.0 P24.
We are committed to correcting any problems encountered with Wusage 8.0! Development of Wusage 9.0 is also underway.
09/06/02: Wusage 8.0 P24 ReleasedWusage 8.0 P24 addresses the following issues, in addition to those previously addressed. We recommend that you upgrade now to Wusage 8.0 P24, especially if you use Microsoft Windows.
- Important for Windows users: Wusage 8.0 P23 had difficulty with configuration file names, log file names and other paths containing spaces. This has been corrected in Wusage 8.0 P24. This was due to Windows-specific issues and was not a problem on other operating systems.
- Important for Windows users: Wusage 8.0 P24 and
above always use your regular web browser as a user interface.
Selecting Wusage from your start menu automatically carries out a
connection to the Wusage NT service, which runs on your own
computer just as the previous GUI application did.
If you are not using Internet Explorer, you may need
to adjust your proxy server settings to ensure that connections to
localhostdo not go through the proxy server.
- ISP mode is fully supported on Windows 95/98/Me, including web connections to Wusage accounts. Of course, NT, 2000 and XP have always supported this feature and are preferred for serious Windows-based work.
- The Wusage Windows NT service no longer displays an "unexpected termination" message when shut down through the services control panel.
- Some users pointed out that, under Windows, the very first web browser connection to the NT service would fail, and a subsequent reload would work. This problem has been corrected.
- In previous patchlevels, in the presence of the "ignore sites" filter and other means of rejecting log file lines, these lines would under some circumstances still be counted for purposes of the "result codes" report. This has been corrected in Wusage 8.0 P24.
- The "documents not found" report is now generated regardless of whether 404 has been classified as a "successful" result code or not.
- Search keywords which are empty or consist entirely of whitespace are no longer considered significant. This change was made to accommodate a recent increase in referring URLs from AOL that include "&keyword=" with no argument.
08/19/02: Wusage 8.0 P23 for FreeBSD Link FixedThe link on our download page for FreeBSD Wusage 8.0 P23 has been corrected.
08/08/02: Wusage 8.0 P23 ReleasedWusage 8.0 P23 addresses the following issues, in addition to those previously addressed. We recommend that you upgrade now to Wusage 8.0 P23.
- Correctly detects the appropriate DNS server in Windows 2000/XP/NT environments (95/98/Me users will still need to set their DNS server under "optimization settings"; Unix users have always had automatic detection).
- DNS (ip address) lookup is now "paced" correctly according to the
connection speed option chosen in "optimization settings" or via the
-bpsoption. We recommend lowering your settings if you are finding that 50% or more of IP addresses cannot be resolved; do not overload your DNS server.
- Advanced mode users: ISP mode "overall limits" settings were erroneously applied to your configurations when accessing them through the web interface or GUI. This has been corrected. You may now increase your "keep X daily reports," etc. settings freely.
- Those who tried settings
offfound that this did not operate properly. This has been corrected in 8.0 P23. Since
onis the default most users have not encountered this behavior.
- Additional status display refinements. Note to those who have already begun parsing status.txt files in their own scripts: colons have been removed from various headings.
- Windows GUI users: problems with the "open configuration" button after using "view statistics" have been corrected. The "view statistics" button now returns to the control page properly after launching the browser.
- "Leftover" shutdown requests can no longer cancel the next update attempt.
- The cause of the "unnecessary call to global shutdown" message was detected and corrected. This condition did not cause problems but, understandably, caused concern among users.
08/05/02: Wusage 8.0 P22 ReleasedWusage 8.0 P22 addresses the following issues, in addition to those already addressed in previous patchlevels:
- Wusage now always waits at least
dnslookupsecondsseconds before "giving up" on any outstanding IP address lookups at the end of the lookup pass.
- Wusage respects the user-specified connection speed when making DNS queries.
- P20 disabled the "view statistics" button when compressed reports were present. P22 corrects this problem.
- A bug in the GCC compiler, version 2.96, as released by Red Hat
with Red Hat 7.2, prevented the
entrieswithoutservernameoption from operating properly in Linux. Wusage has been rebuilt with GCC 3.1.1 and no longer exhibits this problem.
08/02/02: Wusage 8.0 P20 ReleasedWusage 8.0 P20 addresses the following issues. It is a recommended upgrade for all users:
- Full process isolation for each account or configuration's "update statistics" operation greatly increases reliability
- Greatly improved progress reporting, including a global progress window which allows scheduled updates to be monitored
- Default settings for top documents, top sites, etc. increased to 50 in new configuration files
dnslookupsecondsis now respected
- DNS always converted to lowercase
- More support for cancelling various operations in the GUI
- PHP files and Cold Fusion Metafiles are now part of the "pages" object type by default in new configuration files
- Configuration file lines containing words that begin with "end" are now accepted properly
- Shared log file users who have some entries without a
virtual server name can now specify the
entrieswithoutservername(on or off) option to indicate whether these should be accepted. The default, as always, is to accept them
- "Update All Accounts Now" button added to account administration page
- "View Statistics Now" appears only when reports exist
- Cancellation of an "add account" operation now removes the account, preventing confusion. Half-completed, then cancelled accounts left intact by earlier releases can be cleaned up with "remove account" button
- Warning messages and similar for individual configurations are
now appended to
console.txtin the report directory. Global messages are written to
wusage-messages.txtin the home directory. Important errors are also written to standard error. The new -verbose command line option forces all messages to be copied to stderr as well.
- Spurious warnings, long delays and lockups caused by file locking problems have been corrected, greatly improving the usefulness of ISP mode
- Shared log file users: the
wusage-accountsarchives log lines intended for virtual servers other than those for which you have set up accounts. Prior to 8.0 P20, if log rotation was not performed or was only partially performed, these lines could be archived repeatedly, wasting space. This has been corrected
- The console displayed in the web interface or Windows GUI includes messages for the current/just completed update only
04/24/02: Web Hosting DirectoryWe now offer a directory of companies offering web hosting services that include Wusage reports.
04/23/02: Wusage 9.0 Feature Request FormInterested in Wusage 9.0? Want to encourage us to include your favorite feature? This is your chance! Check out the Wusage 9.0 Wish List form. We welcome suggestions from both new and experienced users of our product.
04/15/02: Wusage 8.0 P19 for Many PlatformsWusage 8.0 P19 addresses the following issues:
- Windows users: the local network shares are now enumerated
only when the
Change Network Share...button is used. This greatly improves performance when using Wusage in a large NT domain.
- Better support for Microsoft FTP servers.
- Errors during local file browsing no longer "trap" the user; it is always possible to change the drive, network share or path.
Change Path...button is now available during FTP and HTTP as well as local file browsing.
- Hostnames found in mixed case in IIS log files are now correctly converted to lowercase to ensure that they are not regarded as separate sites.
- It is now possible to escape from the Simple Mode setup process
by clicking the
Cancelbutton during the log file or directory selection process. This now returns the user to the mode selection page rather than forcing the user back to the "log file or directory" page.
-compressedand -uncompressed command line options now work properly.
- The server configuration tips section of the manual now includes instructions to configure Apache for transparent support of compressed report pages. See Optimization Settings for more information about how to enable compressed report pages.
Additional improvements and fixes are scheduled for inclusion in 8.0 P20. Development of Wusage 9.0 is also underway.
03/27/02: Wusage 8.0 P18 for Windows and LinuxWusage 8.0 P18 greatly improves our support for fetching log files remotely via FTP. 8.0 P18 also enhances our handling of log file browsing in general. Compatibility with the wide variety of FTP servers in the field has been greatly enhanced, making it much easier to locate the log files that you are looking for, especially when the root directory is inaccessible. Compatibility with the wuftpd FTP demon is much improved. Access to log files via the local file system (including drive letters and Windows network shares), FTP, and HTTP is now carried out through a single consistent and straightforward interface, simplifying the experience of configuring the program for the first time.
02/27/02: Wusage 8.0 P17 for Many Operating SystemsWusage 8.0 P14 introduced several important features, as well as a number of fixes. Unfortunately, it also introduced several problems, and 8.0 P15 and P16 did not fix all of them. We are changing our procedures to ensure that this does not happen again. We apologize for the inconvenience.
Wusage 8.0 P17 repairs a defect in 8.0 P16 which caused it to reject work-in-progress databases generated by earlier releases. 8.0 P17 accepts these databases correctly. The problem did not cause the loss of historical charts, such as those linked to at the top of the calendar of reports, and is not a major problem for those not relying on the summary, annual and quarterly reports.
Wusage 8.0 P17 also correctly skips "subprocess accounting" entries in IIS log files, preventing the generation of many unnecessary log file format warnings and (in rare, extreme cases) crashes due to the overwhelming number of such warnings. This problem occurred only with some configurations of IIS 5.0. 8.0 P17 also produces more useful log file format warnings, due to the inclusion of the log file name in question. A particular warning is only displayed once for a particular log file.
02/25/02: Wusage 8.0 P16 for Many Operating SystemsThe following issues are resolved in 8.0 P16. Note that some of these improvements address longstanding issues. We strongly recommend 8.0 P16 to all users, and especially to those with 8.0 P14 or 8.0 P15:
- "Update for Time Period" properly updates single days even when it cannot update any longer reporting periods; also, "Update for Time Period" correctly generates links to charts at the top of the calendar page. This was a longstanding issue.
- Unix users: the
-wusage-check-serveroption no longer produces warnings on standard error if an update is progress. This prevents unwanted emails from cron. This was a longstanding issue. no more unwanted emails from cron!
- Updating reports without any new log data no longer causes crashes under certain situations (problem introduced by 8.0 P14).
- 8-bit European URLs no longer cause crashes under certain conditions. This was a longstanding issue.
02/20/02: Wusage 8.0 P15 for Many Operating SystemsWusage 8.0 P15 corrects a problem which caused P14 to crash, in certain cases, when continuing from an existing work-in-progress database produced by an earlier release of the program.
02/19/02: Wusage 8.0 P14 for Many Operating SystemsWusage 8.0 P14 addresses the following issues. We recommend reading these notes before you upgrade, as upgrading users may need to make configuration changes to take best advantage of some of the improvements in 8.0 P14. Like all patchlevels, P14 is a free upgrade from any earlier release of 8.0 and you do not need to pay again to use it.
- A new mechanism for counting unique visitors by the best
available method! New configurations set up with 8.0 P14 or later
will contain a
totalsgroup(historical totals) option entry like this:
visitors yeartoyear unique Unique Visitors (Best Method)This special pattern produces a unique visitor count by the following highly sophisticated and accurate method:
If the number of user-identifying cookies logged at least twice is equal to at least 5% of the number of unique IP addresses, then the number of unique visitors is equal to the number of cookies logged at least twice, plus the number of accesses made by users not accepting cookies divided by the average number of accesses made by each user who did accept cookies. The resulting figure is a highly accurate projection of the true number of unique visitors, including those visitors who reject cookies and use other forms of identity-masking software. If cookies are not available, or the number of cookies logged at least twice is less than 5% of the number of unique IP addresses, then the number of unique IP addresses is reported as the number of unique visitors. The unique visits figure is available for use in the historical totals option, as well as in the executive summary (macro customizers should see the epoch.rmc file provided with 8.0 P14).
- Starting in 8.0 P14, the "users as determined by cookies"
users) report shows only cookies which were logged at least twice. This mechanism excludes the very large number of "one-shot" cookies logged in a single visit by users who do not actually accept cookies, which can cause the web server to produce and log a new cookie for every access. This enhancement to the program also saves memory. If you find that this results in a significant reduction in the figure you were relying upon as a measure of unique visits, read the preceding entry in this page for a new and improved method of measuring unique visits.
- The "referring URLs by document not found" report has been corrected and works properly in both daily and longer-term reports.
- A new
donottouch(documents that should not be fetched) filter is available. This filter can be used to prevent Wusage 8.0 from attempting to access certain pages, as it would otherwise attempt to do in order to determine their titles and structure. Examples:
donottouch #Leave one script alone /cgi-bin/scriptthatsendsemailwhenfetched #Leave all .cgi files alone *.cgi #Leave contents of cgi-bin alone /cgi-bin/*
- A problem which corrected some of the report links in the report listings underneath each historical chart from working in Netscape has been corrected. This problem did not occur on the calendar page or in Microsoft Internet Explorer.
- The percentage of your the connection speed used by the IP address lookup feature has been reduced to a more realistic level.
- Various stability and reliability fixes.
- Various minor inconsistencies in the handling of projected visit counts for identity-masked users have been corrected, resulting in "visits by day" subreports that match the visit figures reported for the week in question, the days in question, etc.
01/03/02: Wusage 8.0 P13 for Windows OnlyWusage 8.0 P13 corrects a problem which prevented remote web access to ISP mode from working correctly under Windows NT/2000/XP. This problem does not occur in Unix. There is no P13 for Unix.
Windows users can download 8.0 P13 from our download page.
01/02/02: Wusage 8.0 P12 for All PlatformsWusage 8.0 P12 addresses the following concerns. We recommend that users upgrade to 8.0 P12.
- Corrects a problem which caused earlier patchlevels to leave
a significant number of empty temporary directories behind in
/tmp, or the temporary-files directory of the operating system in question. Note: this fix also automatically removes existing unnecessary temporary files.
- Corrects a rare problem which caused part of the user interface of simple mode to become unavailable when certain settings were in effect in ISP mode.
12/20/01: Wusage 8.0 P11 for All PlatformsWusage 8.0 P11 addresses the following concerns.
- Web-based access to the Windows version works properly.
- Passwords of unprivileged accounts can be changed correctly.
- Problems when upgrading an existing report directory from 7.1 or earlier have been corrected; if the program has failed for you while attempting to update a pre-existing set of reports under 8.0 for the first time, you should definitely obtain P11.
- Stability problems relating to visits have been resolved.
12/17/01: Wusage 8.0 P10 for WindowsP10 for Windows corrects an FTP log retrieval problem encountered by Windows users, particularly those doing remote analysis of logs on a distant server.
Windows users should visit our download page.
12/11/01: Wusage 8.0 P9 for Linux (Not Required Elsewhere)Due to a packaging problem, Wusage 8.0 P8 for Linux was missing a required file for the creation of reports. This problem has been corrected in 8.0 P9. No other changes appear in 8.0 P9, which is not necessary on other operating systems.
Linux users should visit our download page.
12/10/01: Wusage 8.0 P8 for Many Operating SystemsWusage 8.0 P8 addresses the following concerns:
- Wusage reliably reads existing document structure databases
- Historical totals entries can be edited properly through the web- or GUI-based configuration editor
- "Referrers by document" totals are accurate for weekly, monthly, etc. reports (daily figures were already correct)
- Users of ISP mode log rotation only: problems with log rotation no longer
occur when unsorted log entries (including entries near the change to standard
time) are encountered. These problems sometimes caused very large redundant
log archive files to accumulate. If you suspect this is causing a slowdown in
your copy, check your
wusage-accounts/accountname/log-archivesubdirectories for a large number of files with a single date; if you normally run our updates once a day or less, you can safely remove all but the first archive file for any individual day. Wusage 8.0 P8 will also remove redundantly archived log files automatically, but may take a long time to do so if those files are large.
- Windows users: whitespace handled properly in situations involving the command line shell, such as producing the navigation report when Wusage has been installed in a folder with spaces in the folder name
- Unix users:
-uninstallcommand line option removes unwanted crontab entries (DOES NOT delete the program or your reports)
- Unix users:
-noinstallcommand allows Wusage to be run in its server mode without the automatic installation of crontab entries
- Unix users: running
wusagewith no command line arguments is now equivalent to
wusage -server, which means that the program automatically goes into the background and remains available for use indefinitely unless terminated with a
- Unix users: Wusage now automatically installs itself to be automatically
restarted if the program is not already listening for connections.
This check is made evey 5 minutes. This is accomplished via a
crontab entry similar to that already used to check for scheduled
updates each hour. This is very useful and makes it easy to
correctly install the program: just type
./wusageonce and the program takes care of making sure it is available after reboots, et cetera. Users who do not want this behavior can use the
-noinstalloption. Also, the
12/06/01: Wusage 8.0 P7 for Windows Fixes FTP ProblemWusage 8.0 for Windows P4 and P6 had a small but significant problem, which prevented those releases from fetching log files via FTP if the connection took more than 1/10th of a second to establish. This problem has been fixed.
12/05/01: Upgrades Can Now Be Purchased Online!By popular demand, it is now possible to purchase an upgrade to Wusage 8.0 online. Just take advantage of our new Wusage Upgrade Store. Don't forget: customers who registered on or after September 1st, 2001 do not need to purchase an upgrade. Global license holders should contact us by phone or fax to purchase an upgrade. All other licenses can now be upgraded online.
12/04/01: Wusage 8.0 P6 Released for Many Operating SystemsWusage 8.0 P6 is now available for Windows, Linux and many other flavors of Unix. Wusage 8.0 P6 addresses all known issues with Wusage 8.0. Upgrading is recommended.
Check our download page; additional ports will be appearing over the coming days and weeks.
Wusage 8.0 P6 addresses the following concerns:
- The stolen objects report works properly. Please note: "external links" refers to the number of accesses made with an external referring URL, not to the number of unique referring URLs involved.
- Graceful response when various command line options are not properly specified.
- Top trails report shows the correct number of trails.
Significant trails must contain at least
trailminimumstepsweb pages; other object types do not count toward trails.
- Solaris customers: replaced troublesome Solaris sorting function with a superior alternative. This was the cause of crashes affecting several Solaris customers.
- Log files which contain both fully qualified request URLs and
a server name field are analyzed properly when the
manyserversoption is in effect.
- Minor aesthetic changes to the "top documents" and "top directories" reports.
12/04/01: Wusage 8.0 P4 Released for Windows8.0 P4 is now available for Windows 95/98/Me/NT/2000/XP. This is the first Windows release of 8.0. A few minor fixes of relevance to Unix users as well will be released as P4 for Unix platforms over the next few days.
11/28/01: Wusage 8.0 P3 Released for Many Unix Flavors8.0 P3 is now available for Linux and other varieties of Unix. Check our download page; additional ports will be appearing today and for the next several days. The Windows release will be available within 24 hours.
Wusage 8.0 P3 addresses the following concerns:
manyservers onand/or the absence of any setting for
topurlno longer causes a crash when the home page of the site is analyzed. Wusage 8.0 P3 and above will not attempt structural analysis (titles, successful download percentage, and components) when
manyserversis on and/or
- The CGI Parameters and Values report now allows settings for
the number of CGI scripts (
topcgiscripts), the number of parameters per script (
topcgiparameters) and the number of values per parameter (
topcgivalues). The defaults are generous but not infinite, ensuring that the resulting table will not overwhelm the browser.
rewrite(rewrite rules) works properly.
11/27/01: Wusage 8.0 P2 for Solaris Sparc ReissuedDue to an oversight in the release process, yesterday's distribution of Wusage 8.0 P2 for Solaris Sparc 2.7 actually contained Wusage 7.1. Affected parties are encouraged to re-download the software. If you are not sure what you have, type "./wusage -v" to check your version.
11/26/01: Wusage 8.0 P2 Released for Many Unix Flavors!8.0 P2 is now available for Linux and other varieties of Unix. Check our download page; additional ports will be appearing today and for the next several days.
Wusage 8.0 P2 addresses the following issues. See the next news entry for more information about 8.0 in general:
- Object types, filters, etc. can now be re-ordered. That is, the user interface provides a way to move one object type to the top of the list so that it appears first in reports, et cetera.
- The configuration editor works correctly with Internet Explorer, with or without a proxy server involved.
- Corrections to the macro files.
- In the top-level report, the chart links for the first three report frequencies are given one row and the remaining two placed in a second row for best readability.
- Many important bug fixes prompted by specific test cases.
11/19/01: Wusage 8.0 RELEASED for Linux!Wusage 8.0 has been released for the Linux operating system. Other operating systems will follow quickly over the course of the next seven days.
Version 8.0 is a FREE UPGRADE for all customers registering Wusage 7.1 on or after September 1st, 2001! Register 7.1 now and get 8.0 for free -- guaranteed.
- Extremely fast reverse DNS lookups! Wusage 8.0 can translate from IP address to hostname hundreds of times per second. This feature makes turning on reverse DNS lookups a very realistic option for most users.
- When setting log file locations (the
logfilesoption), * and ? wildcards are now permitted in the last component of the path. Example:
- Greatly improved progress display, for both Unix and Windows.
- Multiple virtual server names are supported for each website.
- Automatic discovery of Microsoft IIS server names when Wusage
is running on the server itself. Users no longer need to specify
W3SVCxas the virtual server name to analyze; Wusage can look up the W3SVCx name based on the domain name.
- The site navigation graph reveals how your
website is truly used. This highly informative graph provides a visual
guide to the most frequently followed paths through your website. The
navigation graph is often surprising; it often contradicts the way
webmasters think their site is designed. This feature provides
a tremendous amount of information; we utilize the open source
ghostscriptpackages (both free, and easily installed separately) in order to create the best available visual representation of your users' true behavior. The graph is presented as a PDF file (Portable Document Format) to facilitate easy printing of this large report, which is often best appreciated when taped to a whiteboard or simply laid out on the floor. We simply can't say enough about this great new feature.
- Document structure is now displayed. Easily view a list of "components," such as images and frames, that make up each document on your website.
- Percentage of successful downloads is displayed for every object. For pages, this percentage takes into account whether or not the user succeeded in downloading all of the images that make up the page. Extremely useful when you wish to evaluate the quality of an end user's experience! Wusage 8 analyzes eight pages simultaneously to limit the performance impact of this great new feature; it can also be turned off if performance becomes a concern.
- "Stolen" objects report: see which of your images, audio files, etc. are being embedded in OTHER websites.
- Separate subreports for pages, images, audio, video, and so on. User-editable "subtypes" allow you to add more subreports and edit the definition of existing subreports.
- "Subtypes" can also be used as a better basis for historical charts, such as the "page views" chart.
- Historical charts are now accessible from the "home page" of each report set. This change addresses a common concern among users who had difficulty locating the "View Chart" buttons in the 7.0 series.
- CGI scripts, keywords and parameters report tells you everything you need to know about your interactive pages.
- Screen resolution and depth report tells you how many pixels your users can see, and with how many colors. Stop wondering what your site looks like to your customers; now you know for sure!
- Improved user-identifying cookie handling code deals gracefully with servers that log a cookie on the first request and servers that log cookies only when they come back from the client. Wusage no longer counts single-access "visits" as such, because they are typically the result of identity-masking software that skews the number of visits. Instead, the program counts these "stealthy" accesses and scales them according to the average accesses per visit for more typical "non-stealthy" users.
- Document titles are displayed in addition to URLs. Wusage 8 analyzes eight pages simultaneously to limit the performance impact of this great new feature; it can also be turned off if performance becomes a concern.
- Additional user-definable output features ease the localization of reports.
- Important aesthetic improvements.
- Efficiency and memory usage improvements.