@@ -64,14 +64,14 @@ So, have a look at the following chart to:
Your Web site size
Recommended values for parameters
Recommended update frequency (Rotate log delay)
Memory required**
Duration***
DNSLookup*
0 - 1,000 visits/month
1
Once a week Log files are 0-3 MB 10000 lines to process
<4 MB
<2mn
-
0
Once a month Log files are 0-12 MB 40000 lines to process
<4 MB
<20s. (4100 lines/seconds)
+
0
Once a month Log files are 0-12 MB 40000 lines to process
<4 MB
<20s.
1,000 - 10,000 visits/month
1
Every 12 hours Log files are 1-2 MB 660-6600 lines
4-8 MB
1-2mn
-
0
Once a week Log files are 3-30 MB 10000-100000 lines
4-8 MB
5-50s (4100 lines/seconds)
+
0
Once a week Log files are 3-30 MB 10000-100000 lines
4-8 MB
5-50s
10,000 - 50,000 visits/month
1
Every 4 hours Log files are 1-4 MB 2200-11000 lines
8-16 MB
1-4mn
-
0
Once a day Log Files are 4-20 MB 13000-65000 lines
8-16 MB
10-40s (4100 lines/seconds)
+
0
Once a day Log Files are 4-20 MB 13000-65000 lines
8-16 MB
10-40s
50,000 - 250,000 visits/month
1
Every hour Log Files are 1-4 MB 2700-14000 lines
16-32 MB
2-4mn
-
0
Every 6 hours Log Files are 5-25 MB 17000-80000 lines
16-32 MB
10-80s (4100 lines/seconds)
-
250,000 - 1,000,000 visits/month
0
Every hour Log Files are 4-16 MB 14000-56000 lines
32-56 MB
10-60s
+
0
Every 6 hours Log Files are 5-25 MB 17000-80000 lines
16-32 MB
20-80s
+
250,000 - 1,000,000 visits/month
0
Every hour Log Files are 4-16 MB 14000-56000 lines
32-64 MB
30-120s
1,000,000 - 5,000,000 visits/month
0
AWStats is not a good choice for such web sites. Try a tool with less features but faster like Analog
+5,000,000 visits/month
0
AWStats is not a good choice for such web sites. Try a tool with less features but faster like Analog
@@ -79,21 +79,21 @@ So, have a look at the following chart to:
- reverse DNS lookup is already done in your log file
- or if you don't need the "domain/countries" report
- or if your web site has more than 250,000 visits a month.
-** Free memory required for update process (in MB).
+** Free memory required for update process (in MB). Warning: If you use the "URLWithQuery" option, this value is doubled.
*** Duration is with Athlon 1GHz/128Mb and LogFormat=1.
This is a summary of main ways to speed up AWStats:
-- You can disable DNSLookup in AWStats (set DNSLookup=0) but this requires
+- You can disable "DNSLookup" in AWStats (set DNSLookup=0) but this requires
that hosts addresses in your log file are already resolved (need to setup your
-web server to do so). Speed can be increased up by 2 to 50 times !
-- If you use Apache, set PurgeLogFile to 1 (By default, to avoid bad surprise,
+web server to do so). Log analyze speed can be increased by 2 to 50 times but your web server will be slowed.
+- If you use Apache, set "PurgeLogFile" to 1 (By default, to avoid bad surprise,
PurgeLogFile is 0 in configure file, but you can set it to 1 to ask AWStats
to purge log file after processing it, this increase speed for next run).
- Launch AWStats more often (from crontab or a scheduler). The more often you
launch AWStats, the less AWStats has new lines in log to process.
-- Use last AWStats version
+- Use last AWStats version.
diff --git a/docs/awstats_changelog.txt b/docs/awstats_changelog.txt
index 97f1c2a2..f5346ce9 100644
--- a/docs/awstats_changelog.txt
+++ b/docs/awstats_changelog.txt
@@ -1,6 +1,12 @@
AWStats Changelog
-----------------
+4.1
+
+- New feature: Report exit pages
+- New feature: Report visits duration
+
+
4.0
WARNING: 4.0 is not compatible with OLD history data files. If you use 4.0
diff --git a/docs/awstats_compare.html b/docs/awstats_compare.html
index 8f665e4d..451740e7 100644
--- a/docs/awstats_compare.html
+++ b/docs/awstats_compare.html
@@ -20,7 +20,7 @@
@@ -351,11 +351,30 @@ no s at the end (Rename your directory physically and change the DirIcons parame
to reflect this change).
+
+FAQ-SET500 : HOW TO ROTATE MY LOGS WITHOUT LOOSING DATA
+PROBLEM: I want to archive/rotate my logs using my web server
+system options or a third software (rotatelog, cronolog) but don't want to loose any visits information
+during the rotate process.
+SOLUTION:
+If you use a rotate system (internal web server feature or third software), this means you probably not use
+AWStats PurgeLogFile nor ArchiveLogRecords parameter.
+To be sure to not loose any records in your log file during the rotate process, you can just run the AWStats update process
+on the log file after it was archived.
+Note: For Apache users, use of cronolog seems to be a better choice
+than rotatelog (cronolog is available for Unix/Liux and Windows and is more flexible).
+To use cronolog or rotatelog you must setup your web server log file name using a pipe like this example:
+CustomLog "|/usr/sbin/cronolog [cronolog_options] /var/logs/access.%Y%m%d.log" combined
+
+
+
+
FAQ-SET550 : HOW TO RUN AWSTATS FREQUENTLY
PROBLEM: AWStats must be ran frequently to update statistics.
How can I do this ?
SOLUTION:
+ With Windows, you can use the internal task scheduler.
The use of this tool is not an AWStats related problem, so please take a look at your Windows manual.
Warning, if you use "awstats.pl -config=mysite -update" in your scheduled task, you might
@@ -364,7 +383,8 @@ experience problem of failing task. Try this instead
or "C:\[perl_path]\perl.exe C:\[awstats_path]\awstats.pl -config=mysite -update"
A lot of other scheduler (sharewares/freewares) are very good.
-With unix-like operating systems, you can use the "crontab".
+
+With unix-like operating systems, you can use the "crontab".
This is examples of lines you can add in the cron file (see your unix reference manual for cron) :
To run update every day at 04:00, use : 0 4 * * * /opt/awstats/wwwroot/cgi-bin/awstats.pl -config=mysite -update
@@ -404,8 +424,8 @@ log, since last run, to process). See the Bench
get examples of launching frequency according to your web traffic
- You can disable DNSLookup in configure file (set DNSLookup=0)
but this requires absolutely that hosts addresses in your log file are already
-resolved (need to setup your web server to do so). Speed can be increased
-up by 2 to 50 times !
+resolved (need to setup your web server to do so).
+Log analyze speed can be increased by 2 to 50 times but your web server will be slowed.
If you don't understand what is an "already resolved reverse DNS lookup", keep
this parameter to 1.
- If you use Apache, set PurgeLogFile to 1 (By default, to avoid bad surprise,
@@ -419,7 +439,8 @@ to purge the log file after processing it. This increase speed for next run). PROBLEM: What is AWStats speed ?
PROBLEM: What is the frequency to launch AWStats process to update my statistics ?
SOLUTION:
-All benchmarks information and advice on frequency for update process are related into the Benchmark page.
+All benchmarks information and advice on frequency for update process are related into
+the Benchmark page.
@@ -429,8 +450,8 @@ All benchmarks information and advice on frequency for update process are relate
has no hostnames, only IP addresses, countries reported are all "unknown".
SOLUTION: When AWStats find an IP address
in your log file, it tries a reverse DNS lookup to find the hostname and domain
-if the DNSLookup parameter, in your AWStats config file, is DNSLookup=1
-(Default value). So, first, check if you have the good value. The DNSLookup=0
+if the DNSLookup parameter, in your AWStats config file, is DNSLookup=1
+(Default value). So, first, check if you have the good value. The DNSLookup=0
must be used only if your log file contains already resolved IP address. For example,
when you set up Apache with the HostNameLookups=on directive. When you
ask your web server to make itself the reverse DNS lookup to log hostname instead
@@ -438,16 +459,11 @@ of IP address, you will still find some IP addresses in your log file because
the reverse DNS lookup is not always possible. But if your web server fails in
it, AWStats will also fails (All reverse DNS lookups use the same system API).
So to avoid AWStats to make an already done lookup (with success or not), you
-can set DNSLookup=0 in AWStats config file. Since 2.23, because a lot of users
-don't know this option, when AWStats find an already resolved IP Address in your log
-file, it disables itself the reverse DNS lookup because it means that reverse lookup
-is already done in log file. If IIS or Apache has made one DNS lookup resolution
-for one record in your log file, they must have done it for all the file. If
-you find only few lines with hostnames and others with IP Address, it means your
-web server failed in resolving them. Check your DNS reverse system with the nslookup
-command (available on NT/2000 and Unix).
-Apache users might be interesting in knowing there is a tool called logresolve with
-Apache distribution, that can convert a logfile with IP Addresses into a logfile with resolved hostnames.
+can set DNSLookup=0 in AWStats config file.
+If you prefer, you can make the reverse DNS lookup on a log file before running
+your log analyzer (If you only need to convert a logfile with IP Addresses into a
+logfile with resolved hostnames). You can use for this logresolvemerge tool
+provided with AWStats distribution (This tools is an improved version of logresolve provided with Apache).
-
-
-AWStats is distributed under the GNU General Public License (GPL).
-So you must follow the line "Free software - Copylefted - GPL" to know what are major license agreements with AWStats.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+AWStats Documentation - License description
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+AWStats logfile analyzer 4.1 Documentation
+
+
+
+
+
+
+
+
+
+
AWStats License / Copyright
+
+
+AWStats is distributed under the GNU General Public License (GPL).
+So you must follow the line "Free software - Copylefted - GPL" to know what are major license agreements with AWStats.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/awstats_security.html b/docs/awstats_security.html
index de2e897c..03cf3ab3 100644
--- a/docs/awstats_security.html
+++ b/docs/awstats_security.html
@@ -1,168 +1,168 @@
-
-
-
-
-
-
-
-AWStats Documentation - Security page
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-AWStats logfile analyzer 4.0 Documentation
-
-
-
-
-
-
-
-
-
-
-
Little Tips about Security
-
-
-A lot of AWStats users have several web site to manage. This is particularly true for web hosting providers.
-The most common things you would like to do is to prevent user xxx (having a site www.xxx.com) to see
-statistics of user yyy (having a site www.yyy.com).
-
-Policy:
-You have several different config/domains owned by different users and you want to build statistics for each
-of them. You don't need that your customer have "real-time" statistics.
-This is a very good choice for web hosting providers with few but very large web sites of important customers.
-Advantage:
-Very highly secured.
-Disadvantage:
-Statistics are static, no dynamic update/view.
-How:
-All statistics pages for a config/domain file are built in static html files using -output -staticlinks option.
-There is no CGI use of AWStats and static built pages are stored in a web protected realm to
-be securely viewed by correct allowed users only (or sent by mails).
-If users have a command line access (telnet) on statistics server, you must set correct permissions on AWStats
-database files. Set all AWStats database files (built by the update process) for config/domain1 to have read/write
-for user1 (or an admin user) and NO read and NO write permissions for any other users.
-Then, check that the SaveDatabaseFilesWithPermissionsForEveryone parameter is set 0 in your config/domain files.
-If AWStats database files for config/domain1 are read protected, only allowed users can see statistics for config/domain1.
-If AWStats database files for config/domain1 are write protected, only allowed users can update statistics for config/domain1.
-
-Policy:
-You have several config/domain and several users. You want to specify which user can see or update dynamically
-statistics for each config/domain.
-This is one of the most popular way of working.
-Advantage:
-Statistics are dynamic. High level of manageability.
-Disadvantage:
-AWStats database files must still be readable by anonymous web server user, so if an experimented user can have an access to
-the server (telnet) where AWStats database files are stored, he can succeed in installing and running a "hacked" version
-of AWStats that ignores value of parameter AllowAccessFromWebToAuthenticatedUsersOnly.
-How:
-awstats.pl file must be saved in a web protected realm to force a visitor to enter its username/password
-to access AWStats CGI program.
-Example of directives you can add into Apache to have awstats.pl in a web protected realm:
-
-<Files "awstats.pl">
-AuthUserFile /path/to/.passwd
-AuthGroupFile /path/to/.group
-AuthName "Restricted Area For Customers"
-AuthType Basic
-require valid-user
-</Files>
-
-Then edit each config/domain file you want to be protected to set AllowAccessFromWebToAuthenticatedUsersOnly to 1.
-You can also edit list of authorized users in the AllowAccessFromWebToFollowingAuthenticatedUsers parameter.
-
-Other tip: If you define AWSTATS_CONFIG environment variable in your web server environment (Adding
-SetEnv AWSTATS_CONFIG myconfigvalueformydomain with other directives in your Apache VirtualHost config), AWStats
-will use the config file called awstats.myconfigvalueformydomain.conf to choose which statistics used,
-even if a visitor try to force the config/domain file with the URL 'http://mydomain.com/cgi-bin-awstats/awstats.pl?config=xxx'.
-This can be usefull for thoose who edit their config/domain file with AllowAccessFromWebToFollowingAuthenticatedUsers="__REMOTE_USER__".
-
-Policy:
-You have only one hosts or several hosts or users but you don't need to manage particular permissions
-for your different config/domain statistics.
-Advantage:
-Setup is very easy (No need of particular setup). Statistics are dynamic.
-Disadvantage:
-No way to prevent stats for config/domain to be seen by a user that known the
-config/domain name and the url syntax to see stats of a particular config/domain.
-How:
-No particular things to do.
-
-
-
-
-There is a lot of possible use for AWStats combining all its options/parameter with all web servers options/parameters.
-Just use the one you need...
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+AWStats Documentation - Security page
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+AWStats logfile analyzer 4.1 Documentation
+
+
+
+
+
+
+
+
+
+
+
Little Tips about Security
+
+
+A lot of AWStats users have several web site to manage. This is particularly true for web hosting providers.
+The most common things you would like to do is to prevent user xxx (having a site www.xxx.com) to see
+statistics of user yyy (having a site www.yyy.com).
+
+Policy:
+You have several different config/domains owned by different users and you want to build statistics for each
+of them. You don't need that your customer have "real-time" statistics.
+This is a very good choice for web hosting providers with few but very large web sites of important customers.
+Advantage:
+Very highly secured.
+Disadvantage:
+Statistics are static, no dynamic update/view.
+How:
+All statistics pages for a config/domain file are built in static html files using -output -staticlinks option.
+There is no CGI use of AWStats and static built pages are stored in a web protected realm to
+be securely viewed by correct allowed users only (or sent by mails).
+If users have a command line access (telnet) on statistics server, you must set correct permissions on AWStats
+database files. Set all AWStats database files (built by the update process) for config/domain1 to have read/write
+for user1 (or an admin user) and NO read and NO write permissions for any other users.
+Then, check that the "SaveDatabaseFilesWithPermissionsForEveryone" parameter is set 0 in your config/domain files.
+If AWStats database files for config/domain1 are read protected, only allowed users can see statistics for config/domain1.
+If AWStats database files for config/domain1 are write protected, only allowed users can update statistics for config/domain1.
+
+Policy:
+You have several config/domain and several users. You want to specify which user can see or update dynamically
+statistics for each config/domain.
+This is one of the most popular way of working.
+Advantage:
+Statistics are dynamic. High level of manageability.
+Disadvantage:
+AWStats database files must still be readable by anonymous web server user, so if an experimented user can have an access to
+the server (telnet) where AWStats database files are stored, he can succeed in installing and running a "hacked" version
+of AWStats that ignores value of parameter AllowAccessFromWebToAuthenticatedUsersOnly.
+How:
+awstats.pl file must be saved in a web protected realm to force a visitor to enter its username/password
+to access AWStats CGI program.
+Example of directives you can add into Apache to have awstats.pl in a web protected realm:
+
+<Files "awstats.pl">
+AuthUserFile /path/to/.passwd
+AuthGroupFile /path/to/.group
+AuthName "Restricted Area For Customers"
+AuthType Basic
+require valid-user
+</Files>
+
+Then edit each config/domain file you want to be protected to set "AllowAccessFromWebToAuthenticatedUsersOnly" to 1.
+You can also edit list of authorized users in the "AllowAccessFromWebToFollowingAuthenticatedUsers" parameter.
+
+Other tip: If you define AWSTATS_CONFIG environment variable in your web server environment (Adding
+SetEnv AWSTATS_CONFIG myconfigvalueformydomain with other directives in your Apache VirtualHost config), AWStats
+will use the config file called awstats.myconfigvalueformydomain.conf to choose which statistics used,
+even if a visitor try to force the config/domain file with the URL 'http://mydomain.com/cgi-bin-awstats/awstats.pl?config=xxx'.
+This can be usefull for thoose who edit their config/domain file with AllowAccessFromWebToFollowingAuthenticatedUsers="__REMOTE_USER__".
+
+Policy:
+You have only one hosts or several hosts or users but you don't need to manage particular permissions
+for your different config/domain statistics.
+Advantage:
+Setup is very easy (No need of particular setup). Statistics are dynamic.
+Disadvantage:
+No way to prevent stats for config/domain to be seen by a user that known the
+config/domain name and the url syntax to see stats of a particular config/domain.
+How:
+No particular things to do.
+
+
+
+
+There is a lot of possible use for AWStats combining all its options/parameter with all web servers options/parameters.
+Just use the one you need...
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/awstats_setup.html b/docs/awstats_setup.html
index 2806bb0b..a8e17493 100644
--- a/docs/awstats_setup.html
+++ b/docs/awstats_setup.html
@@ -7,10 +7,10 @@
AWStats Documentation - Setup page
+
-
@@ -58,7 +58,7 @@ your homepage. This is an example of records you should get then in the new log
62.161.78.75 - - [dd/mmm/yyyy:hh:mm:ss +0000] "GET / HTTP/1.1" 200 1234 "http://www.from.com/from.html" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
* Copy all the content of provided AWStats cgi-bin directory into your web
-server cgi-bin directory (this includes awstats.pl, awstats.model.conf, and the lang and db sub-directories).
+server cgi-bin directory (this includes awstats.pl, awstats.model.conf, and the lang and lib sub-directories).
* If necessary (should not with most perl interpreter), in awstats.pl file, edit the first line #!/usr/bin/perl
@@ -78,11 +78,11 @@ Whatever the name you choose, this new file must be stored in
- /etc/opt/awstats or /etc/awstats or /etc or same directory than awstats.pl (so cgi-bin) for Unix/Linux users.
- same directory than awstats.pl (so cgi-bin) for Windows and other OS.
Edit this new config file with your own setup :
-- Change "LogFile" value with full path of your web server log file (You
+- Change "LogFile" value with full path of your web server log file (You
can also use a relative path from your awstats.pl directory).
-- Check if "LogFormat" has the value "1" (it means "NCSA apache combined/ELF/XLF log format").
-- Change "DirIcons" parameter to reflect relative URL of icon directory.
-- Edit "SiteDomain" parameter with the main domain name or the intranet
+- Check if "LogFormat" has the value "1" (it means "NCSA apache combined/ELF/XLF log format").
+- Change "DirIcons" parameter to reflect relative URL of icon directory.
+- Edit "SiteDomain" parameter with the main domain name or the intranet
web server name used to reach the web site to analyze.
- You can change other parameters if you want.
@@ -117,7 +117,7 @@ your homepage. This is an example of records you should get then in the new log
2000-07-19 14:14:14 62.161.78.73 - GET / 200 1234 HTTP/1.1 Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0) http://www.from.com/from.htm
* Copy all the content of provided AWStats cgi-bin directory into your web
-server cgi-bin directory (this includes awstats.pl, awstats.model.conf, and the lang and db sub-directories).
+server cgi-bin directory (this includes awstats.pl, awstats.model.conf, and the lang and lib sub-directories).
* Move all AWStats icon sub-directories into a directory readable by your
web server, for example C:\yourwwwroot\icon.
@@ -128,11 +128,11 @@ awstats.virtualhostname.conf, and, if not found, will look for awstats.conf.
Whatever the name you choose, this new file must be stored in
- same directory than awstats.pl (so cgi-bin)
Edit this new config file with your own setup :
-- Change "LogFile" value with full path of your web server log file (You
+- Change "LogFile" value with full path of your web server log file (You
can also use a relative path from your awstats.pl directory).
-- Change "LogFormat" to value "2" (it means "IIS Extended W3C log format").
-- Change "DirIcons" parameter to reflect relative URL of icon directory.
-- Edit "SiteDomain" parameter with the main domain name or the intranet
+- Change "LogFormat" to value "2" (it means "IIS Extended W3C log format").
+- Change "DirIcons" parameter to reflect relative URL of icon directory.
+- Edit "SiteDomain" parameter with the main domain name or the intranet
web server name used to reach the web site to analyze.
- You can change other parameters if you want.
@@ -152,7 +152,7 @@ Use "LogFormat" to value "3" if you have WebStar native log format.
Even if AWStats allows "real-time" statistics with its "update from browser feature" (See next
section Read Statistics), you must run the update process from a scheduler frequently.
-The first update of statistics can be made the first time manually from the command line (the first time,
+* The first update of statistics can be made the first time manually from the command line (the first time,
process may be long : awstats.pl -config=virtualhostname -update
@@ -167,13 +167,13 @@ Found 0 old records,
Found 225601 new records.
Dropped records are records discarded because they were not user HTTP request or requests were not qualified
-by AWStats filters (See SkipHosts, SkipFiles,
-and OnlyFiles parameters).
+by AWStats filters (See "SkipHosts", "SkipFiles",
+and "OnlyFiles" parameters).
If you want to see which lines were dropped, you can add the -showdropped option on command line. Corrupted records are records that does not match log format defined by "LogFormat" parameter in AWStats config/domain file.
With all webservers you can experience a little bit corrupted records (<5%) even when everythings work correctly.
This can be the result of several reasons: Web server internal bugs, bad requests made by buggy browsers, web server brutal stop...
-If all your lines are corrupted and "LogFormat" parameter in AWStats config/domain file is correct, may be it's the log
+If all your lines are corrupted and "LogFormat" parameter in AWStats config/domain file is correct, it may be the log
format setup in your web server that is wrong. Don't forget that you "LogFormat" parameter in AWStats config/domain
file MUST match the log file format you analyze.
If you want to see which lines are corrupted, you can add the -showcorrupted option on command line.
@@ -183,12 +183,12 @@ purge your log file after each update process even if it's HIGHLY recommended to
Note : A log analysis process is slow (one second for each 4100 lines of your
logfile with Athlon 1Ghz, plus DNS resolution time for each different IP
-address in your logfile if "DNSLookup" is set to 1 and not already done in your log file).
+address in your logfile if "DNSLookup" is set to 1 and not already done in your log file).
See Benchmark page for more accurate information.
-New updates should be made from an automatic process.
+* Then new updates should be made from an automatic process.
You can add instructions in your crontab (Unix/Linux) or your task scheduler (for
Windows), to launch frequently this Awstats update process.
For sites with:
@@ -199,7 +199,7 @@ For sites with:
This is ABSOLUTELY necessary to keep good performances.
See AWStats Benchmark page for more accurate information.
* You can also view dynamically your statistics from a browser.
-If you named your config file awstats.virtualhostname.conf, use URL:
+If you named your config file awstats.virtualhostname.conf, use URL: http://www.myserver.mydomain/cgi-bin/awstats.pl?config=virtualhostname
-where virtualhostname is used to know which config file to use (AWStats
-will use awstats.virtualhostname.conf file).
+where virtualhostname is used to know which config file to use (AWStats
+will use awstats.virtualhostname.conf file).
If you named your config file awstats.conf, just use URL: http://www.myserver.mydomain/cgi-bin/awstats.pl
-Note: If "AllowToUpdateStatsFromBrowser" parameter is set to 1 in AWStats config/domain file,
+Note: If "AllowToUpdateStatsFromBrowser" parameter is set to 1 in AWStats config/domain file,
you will also be able to run the update process from your browser. Just click on link "Update now".
