Updated documentation.

diff --git a/docs/awstats_changelog.txt b/docs/awstats_changelog.txt
index 8a5040d7096fbbd2c5368532044fd7890aefdc59..c4fabc7eb0252d19b3dfa759c62d322a24b016b5 100644 (file)
--- a/docs/awstats_changelog.txt
+++ b/docs/awstats_changelog.txt
@@ -28,6 +28,7 @@ Fixes:
 New features/improvements:
 - Added 'rawlog' plugin to add a form to show raw log content with filter
   capabilities.
+- Added a dynamic exclude filter on CGI full list report pages.
 - Added maillogconvert.pl for analyzing mail log files (better support
   for sendmail, postfix and qmail log files).
 - Added -addfilenum option in logresolvemerge.pl

diff --git a/docs/awstats_setup.html b/docs/awstats_setup.html
index e6c968ae255759016ce9bb3b7881d72ef83eb733..bc681318d153db38042f17c22343f3db6c4b7acd 100644 (file)
--- a/docs/awstats_setup.html
+++ b/docs/awstats_setup.html
@@ -82,10 +82,10 @@ This new file must be stored in<br>
 <br>\r
 * Step 1-6<br>\r
 Edit this new config file with your own setup :<br>\r
-- Change <a href="awstats_config.html#LogType">LogType</a> value with "W" for analyzing\r
-web server log files, "M" for mail log files, "F" for ftp log files, "O" otherwise.<br>\r
 - Change <a href="awstats_config.html#LogFile">LogFile</a> value with full path of your web server log file (You\r
 can also use a relative path from your awstats.pl directory).<br>\r
+- Change <a href="awstats_config.html#LogType">LogType</a> value with "W" for analyzing\r
+web server log files, "M" for mail log files, "F" for ftp log files, "O" otherwise.<br>\r
 - Check if <a href="awstats_config.html#LogFormat">LogFormat</a> has the value "1" (it means "NCSA apache combined/ELF/XLF log format").<br>\r
 - Change <a href="awstats_config.html#DirIcons">DirIcons</a> parameter to reflect relative path of icon directory.<br>\r
 - Edit <a href="awstats_config.html#SiteDomain">SiteDomain</a> parameter with the main domain name or the intranet \r
@@ -138,10 +138,10 @@ This new file must be stored in<br>
 <br>\r
 * Step 1-5<br>\r
 Edit this new config file with your own setup :<br>\r
-- Change <a href="awstats_config.html#LogType">LogType</a> value with "W" for analyzing\r
-web server log files, "M" for mail log files, "F" for ftp log files, "O" otherwise.<br>\r
 - Change <a href="awstats_config.html#LogFile">LogFile</a> value with full path of your web server log file (You\r
 can also use a relative path from your awstats.pl directory).<br>\r
+- Change <a href="awstats_config.html#LogType">LogType</a> value with "W" for analyzing\r
+web server log files, "M" for mail log files, "F" for ftp log files, "O" otherwise.<br>\r
 - Change <a href="awstats_config.html#LogFormat">LogFormat</a> to value "2" (it means "IIS Extended W3C log format").<br>\r
 - Change <a href="awstats_config.html#DirIcons">DirIcons</a> parameter to reflect relative path of icon directory.<br>\r
 - Edit <a href="awstats_config.html#SiteDomain">SiteDomain</a> parameter with the main domain name or the intranet\r
@@ -207,21 +207,11 @@ Even if AWStats allows "real-time" statistics with its "update from browser feat
 section <a href="#READ">Read Statistics</a>), you should run an update process from a scheduler (command is same than\r
 first process) frequently.<br>\r
 <br>\r
-You can add instructions in your <b>crontab</b> (Unix/Linux) or your <b>task scheduler</b> (for\r
-Windows), to launch frequently this Awstats update process.<br>\r
-For sites with:<br>\r
-- 10,000 visitors a month     Launch AWStats once a day<br>\r
-- 50,000 visitors a month     Launch AWStats once every 4 hours<br>\r
-- 250,000 visitors a month    Launch AWStats once an hour<br>\r
-- 1,000,000 visitors a month  Launch AWStats once an hour<br>\r
-This is ABSOLUTELY necessary to keep good performances.<br>\r
-See AWStats <a href="awstats_benchmark.html">Benchmark page</a> for more accurate information.<br>\r
-<br>\r
-!!! Warning, if you don't use (or can't use with IIS) the <a href="awstats_config.html#PurgeLogFile">PurgeLogFile</a> parameter,\r
-it's very important that you don't forget to purge/rotate your log file yourself (or setup your web server to do it)\r
-frequently (You can find help for this on <a href="awstats_faq.html#CRONTAB">FAQ-SET550</a>).\r
-Even if AWStats never analyzes twice the same log record, the more often you clean your log file, the\r
-faster AWStats will be.<br>\r
+You have two choice:<br>\r
+- Include the update in your <b>logrotate</b> process. See <a href="awstats_faq.html#ROTATE">FAQ-COM120</a> for this.<br>\r
+- Or add instructions in your <b>crontab</b> (Unix/Linux) or your <b>task scheduler</b> (for\r
+Windows), to launch frequently this Awstats update process. See <a href="awstats_faq.html#CRONTAB">FAQ-COM130</a> for this.<br><br>\r
+See AWStats <a href="awstats_benchmark.html">Benchmark page</a> for recommanded update/logrotate frequency.<br>\r
 <br>\r
 \r
 <br>\r