From: eldy <>
Date: Sun, 26 Jan 2003 22:00:13 +0000 (+0000)
Subject: Updated documentation.
X-Git-Tag: AWSTATS_5_4_BETA~40
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fa035d3dc4a5abcd85fd6fbc0d73615f3fc19e9d;p=thirdparty%2FAWStats.git
Updated documentation.
---
diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html
index f7ef2dc3..1a31e79e 100644
--- a/docs/awstats_faq.html
+++ b/docs/awstats_faq.html
@@ -483,7 +483,7 @@ Modify this new config file:
What do I have to do to use AWStats to analyze my Windows Media Server log files.
SOLUTION:
-Setup your Windows Media Server log format to write the following fields:
+If your Windows Media Server version allows it, setup your log format to write the following fields:
c-ip
date
@@ -552,6 +552,22 @@ Modify this new config file:
Now you can use AWStats as usual (run the update process and read statistics).
+If your Windows Media Server version does not allow to define your log format, just try to use
+same setup for AWStats than previously described but use the log format string found in first
+lines of your log files as value for AWStats LogFormat parameter, for example:
+
+LogFormat="c-ip date time c-dns cs-uri-stem c-starttime x-duration c-rate
+c-status c-playerid c-playerversion c-playerlanguage cs(User-Agent)
+cs(Referer) c-hostexe c-hostexever c-os c-osversion c-cpu filelength
+filesize avgbandwidth protocol transport audiocodec videocodec channelURL
+sc-bytes c-bytes s-pkts-sent c-pkts-received c-pkts-lost-client
+c-pkts-lost-net c-pkts-lost-cont-net c-resendreqs c-pkts-recovered-ECC
+c-pkts-recovered-resent c-buffercount c-totalbuffertime c-quality s-ip s-dns
+s-totalclients s-cpu-util"
+
+
This means you don't use the AWStats tags but AWStats can often also understand the IIS and/or
+Windows Media Server tags.
+
FAQ-SET280 : ERROR "NOT SAME NUMBER OF RECORDS OF..."