<meta name="title" content="AWStats Documentation - Benchmark page">\r
<title>AWStats Documentation - Benchmark page</title>\r
<link rel="stylesheet" href="styles.css" type="text/css">\r
+<!-- $Revision$ - $Author$ - $Date$ -->\r
</head>\r
\r
<body topmargin=10 leftmargin=5>\r
-<!-- $Revision$ - $Author$ - $Date$ -->\r
\r
\r
<table style="font: 10pt arial,helvetica,verdana" cellpadding=0 cellspacing=0 border=0 bgcolor=#FFFFFF width=100%>\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
<tr bgcolor=#EEEEEE><td rowspan=2>Your Web site size</td><td>Recommended values for parameters</td><td rowspan=2>Recommended update frequency<br>(Rotate log delay)</td><td rowspan=2>Memory required**</td><td rowspan=2>Duration***</td></tr>\r
<tr bgcolor=#EEEEEE><td>DNSLookup*</td></tr>\r
<tr><td rowspan=2> 0 - 1,000 visits/month</td><td>1</td><td>Once a week<br>Log files are 0-3 MB<br>10000 lines to process</td><td><4 MB</td><td><2mn</td></tr>\r
-<tr> <td>0</td><td>Once a month<br>Log files are 0-12 MB<br>40000 lines to process</td><td><4 MB</td><td><20s.<br>(4100 lines/seconds)</td></tr>\r
+<tr> <td>0</td><td>Once a month<br>Log files are 0-12 MB<br>40000 lines to process</td><td><4 MB</td><td><20s.</td></tr>\r
<tr><td rowspan=2> 1,000 - 10,000 visits/month</td><td>1</td><td>Every 12 hours<br>Log files are 1-2 MB<br>660-6600 lines</td><td>4-8 MB</td><td>1-2mn</td></tr>\r
-<tr> <td>0</td><td>Once a week<br>Log files are 3-30 MB<br>10000-100000 lines</td><td>4-8 MB</td><td>5-50s<br>(4100 lines/seconds)</td></tr>\r
+<tr> <td>0</td><td>Once a week<br>Log files are 3-30 MB<br>10000-100000 lines</td><td>4-8 MB</td><td>5-50s</td></tr>\r
<tr><td rowspan=2>10,000 - 50,000 visits/month</td><td>1</td><td>Every 4 hours<br>Log files are 1-4 MB<br>2200-11000 lines</td><td>8-16 MB</td><td>1-4mn</td></tr>\r
-<tr> <td>0</td><td>Once a day<br>Log Files are 4-20 MB<br>13000-65000 lines</td><td>8-16 MB</td><td>10-40s<br>(4100 lines/seconds)</td></tr>\r
+<tr> <td>0</td><td>Once a day<br>Log Files are 4-20 MB<br>13000-65000 lines</td><td>8-16 MB</td><td>10-40s</td></tr>\r
<tr><td rowspan=2>50,000 - 250,000 visits/month</td><td>1</td><td>Every hour<br>Log Files are 1-4 MB<br>2700-14000 lines</td><td>16-32 MB</td><td>2-4mn</td></tr>\r
-<tr> <td>0</td><td>Every 6 hours<br>Log Files are 5-25 MB<br>17000-80000 lines</td><td>16-32 MB</td><td>10-80s<br>(4100 lines/seconds)</td></tr>\r
-<tr><td> 250,000 - 1,000,000 visits/month</td><td>0</td><td>Every hour<br>Log Files are 4-16 MB<br>14000-56000 lines</td><td>32-56 MB</td><td>10-60s</td></tr>\r
+<tr> <td>0</td><td>Every 6 hours<br>Log Files are 5-25 MB<br>17000-80000 lines</td><td>16-32 MB</td><td>20-80s</td></tr>\r
+<tr><td> 250,000 - 1,000,000 visits/month</td><td>0</td><td>Every hour<br>Log Files are 4-16 MB<br>14000-56000 lines</td><td>32-64 MB</td><td>30-120s</td></tr>\r
<tr><td> 1,000,000 - 5,000,000 visits/month</td><td>0</td><td colspan=3>AWStats is not a good choice for such web sites. Try a tool with less features but faster like <a href="http://www.analog.cx">Analog</a></td></tr>\r
<tr><td> +5,000,000 visits/month</td><td>0</td><td colspan=3>AWStats is not a good choice for such web sites. Try a tool with less features but faster like <a href="http://www.analog.cx">Analog</a></td></tr>\r
</table>\r
- reverse DNS lookup is already done in your log file<br>\r
- or if you don't need the "domain/countries" report<br>\r
- or if your web site has more than 250,000 visits a month.<br>\r
-** Free memory required for update process (in MB).<br>\r
+** Free memory required for update process (in MB). Warning: If you use the "<a href="awstats_config.html#URLWithQuery">URLWithQuery</a>" option, this value is doubled.<br>\r
*** Duration is with Athlon 1GHz/128Mb and LogFormat=1.<br>\r
\r
\r
<br>\r
<b><u>This is a summary of main ways to speed up AWStats:</u></b><br>\r
-- You can disable DNSLookup in AWStats (set DNSLookup=0) but this requires\r
+- You can disable "<a href="awstats_config.html#DNSLookup">DNSLookup</a>" in AWStats (set DNSLookup=0) but this requires\r
that hosts addresses in your log file are already resolved (need to setup your\r
-web server to do so). Speed can be increased up by 2 to 50 times !<br>\r
-- If you use Apache, set PurgeLogFile to 1 (By default, to avoid bad surprise,\r
+web server to do so). Log analyze speed can be increased by 2 to 50 times but your web server will be slowed.<br>\r
+- If you use Apache, set "<a href="awstats_config.html#PurgeLogFile">PurgeLogFile</a>" to 1 (By default, to avoid bad surprise,\r
PurgeLogFile is 0 in configure file, but you can set it to 1 to ask AWStats\r
to purge log file after processing it, this increase speed for next run).<br>\r
- Launch AWStats more often (from crontab or a scheduler). The more often you\r
launch AWStats, the less AWStats has new lines in log to process.<br>\r
-- Use last AWStats version<br>\r
+- Use last AWStats version.<br>\r
<br>\r
\r
<hr>\r
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
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
<html>\r
<head>\r
<meta name="description" content="AWStats Documentation - FAQ page">\r
-<meta name="keywords" content="awstats, awstat, faq, error, errors, frequently, asked, questions, support, help, problem, solution, troubleshooting">\r
+<meta name="keywords" content="awstats, awstat, faq, error, errors, frequently, asked, questions, support, help, problem, solution, troubleshooting, rotate log">\r
<meta name="robots" content="index,follow">\r
<meta name="title" content="AWStats Documentation - FAQs">\r
<title>AWStats Documentation - FAQs</title>\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
to reflect this change).<br>\r
<br>\r
\r
+<a name="ROTATE"></a><br>\r
+<b><u>FAQ-SET500 : HOW TO ROTATE MY LOGS WITHOUT LOOSING DATA</u></b><br>\r
+<font style="color: #660000">PROBLEM:</font> I want to archive/rotate my logs using my web server\r
+system options or a third software (rotatelog, cronolog) but don't want to loose any visits information\r
+during the rotate process.<br>\r
+<font style="color: #4444cc">SOLUTION:</font><br>\r
+If you use a rotate system (internal web server feature or third software), this means you probably not use\r
+AWStats <a href="awstats_config.html#PurgeLogFile">PurgeLogFile</a> nor <a href="awstats_config.html#ArchiveLogRecords">ArchiveLogRecords</a> parameter.\r
+To be sure to not loose any records in your log file during the rotate process, you can just run the AWStats update process \r
+on the log file after it was archived.<br>\r
+Note: For Apache users, use of <a href="http://cronolog.org" target=awstatsbis>cronolog</a> seems to be a better choice\r
+than rotatelog (cronolog is available for Unix/Liux and Windows and is more flexible).<br>\r
+To use cronolog or rotatelog you must setup your web server log file name using a pipe like this example:<br>\r
+<i>CustomLog "|/usr/sbin/cronolog [cronolog_options] /var/logs/access.%Y%m%d.log" combined</i><br>\r
+<br>\r
+\r
+\r
+\r
<a name="CRONTAB"></a><br>\r
<b><u>FAQ-SET550 : HOW TO RUN AWSTATS FREQUENTLY</u></b><br>\r
<font style="color: #660000">PROBLEM:</font> AWStats must be ran frequently to update statistics.\r
How can I do this ?<br>\r
<font style="color: #4444cc">SOLUTION:</font><br>\r
+<br>\r
<u>With Windows</u>, you can use the internal task scheduler.\r
The use of this tool is not an AWStats related problem, so please take a look at your Windows manual.\r
Warning, if you use <i>"awstats.pl -config=mysite -update"</i> in your scheduled task, you might\r
or<br>\r
<i>"C:\[perl_path]\perl.exe C:\[awstats_path]\awstats.pl -config=mysite -update"</i><br>\r
A lot of other scheduler (sharewares/freewares) are very good.<br>\r
-<u>With unix-like operating systems</u>, you can use the "crontab".<br>\r
+<br>\r
+<u>With unix-like operating systems</u>, you can use the "<b>crontab</b>".<br>\r
This is examples of lines you can add in the cron file (see your unix reference manual for cron) :<br>\r
To run update every day at 04:00, use :<br>\r
<i>0 4 * * * /opt/awstats/wwwroot/cgi-bin/awstats.pl -config=mysite -update</i><br>\r
get examples of launching frequency according to your web traffic<br>\r
- You can disable <i>DNSLookup</i> in configure file (set <i>DNSLookup=0</i>) \r
<u>but this requires absolutely that hosts addresses in your log file are already \r
-resolved</u> (need to setup your web server to do so). Speed can be increased \r
-up by <b>2 to 50</b> times !<br>\r
+resolved</u> (need to setup your web server to do so).\r
+Log analyze speed can be increased by 2 to 50 times but your web server will be slowed.<br>\r
If you don't understand what is an "already resolved reverse DNS lookup", keep \r
this parameter to 1.<br>\r
- If you use Apache, set <i>PurgeLogFile</i> to 1 (By default, to avoid bad surprise, \r
<font style="color: #660000">PROBLEM:</font> What is AWStats speed ?<br>\r
<font style="color: #660000">PROBLEM:</font> What is the frequency to launch AWStats process to update my statistics ?<br>\r
<font style="color: #4444cc">SOLUTION:</font>\r
-All benchmarks information and advice on frequency for update process are related into the <a href="awstats_benchmark.html">Benchmark page</a>.\r
+All benchmarks information and advice on frequency for update process are related into\r
+the <a href="awstats_benchmark.html">Benchmark page</a>.\r
<br>\r
\r
\r
has no hostnames, only IP addresses, countries reported are all "unknown".<br>\r
<font style="color: #4444cc">SOLUTION:</font> When AWStats find an IP address \r
in your log file, it tries a reverse DNS lookup to find the hostname and domain \r
-if the <i>DNSLookup</i> parameter, in your AWStats config file, is <i>DNSLookup=1</i> \r
-(Default value). So, first, check if you have the good value. The <i>DNSLookup=0</i> \r
+if the <a href="awstats_tools.html#DNSLookup">DNSLookup</a> parameter, in your AWStats config file, is <a href="awstats_config.html#DNSLookup">DNSLookup</a>=1\r
+(Default value). So, first, check if you have the good value. The <a href="awstats_config.html#DNSLookup">DNSLookup</a>=0 \r
must be used only if your log file contains already resolved IP address. For example, \r
when you set up Apache with the <i>HostNameLookups=on</i> directive. When you \r
ask your web server to make itself the reverse DNS lookup to log hostname instead \r
the reverse DNS lookup is not always possible. But if your web server fails in \r
it, AWStats will also fails (All reverse DNS lookups use the same system API). \r
So to avoid AWStats to make an already done lookup (with success or not), you \r
-can set <i>DNSLookup=0</i> in AWStats config file. Since 2.23, because a lot of users\r
-don't know this option, when AWStats find an already resolved IP Address in your log \r
-file, it disables itself the reverse DNS lookup because it means that reverse lookup \r
-is already done in log file. If IIS or Apache has made one DNS lookup resolution \r
-for one record in your log file, they must have done it for all the file. If \r
-you find only few lines with hostnames and others with IP Address, it means your \r
-web server failed in resolving them. Check your DNS reverse system with the <i>nslookup</i> \r
-command (available on NT/2000 and Unix).<br>\r
-Apache users might be interesting in knowing there is a tool called <i>logresolve</i> with\r
-Apache distribution, that can convert a logfile with IP Addresses into a logfile with resolved hostnames.<br>\r
+can set <a href="awstats_config.html#DNSLookup">DNSLookup</a>=0 in AWStats config file.\r
+If you prefer, you can make the reverse DNS lookup on a log file before running\r
+your log analyzer (If you only need to convert a logfile with IP Addresses into a\r
+logfile with resolved hostnames). You can use for this <a href="awstats_config.html#logresolvemerge">logresolvemerge</a> tool\r
+provided with AWStats distribution (This tools is an improved version of <i>logresolve</i> provided with Apache).<br>\r
<br>\r
\r
<a name="DIFFERENT_RESULTS"></a><br>\r
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">\r
<html>\r
<head>\r
-<meta name="description" content="AWStats Documentation - Glossary">\r
-<meta name="keywords" content="awstats, awstat, glossary, definition, lexical, index">\r
+<meta name="description" content="AWStats Documentation - Glossary of terms">\r
+<meta name="keywords" content="awstats, awstat, glossary, terms, definition, lexical, index">\r
<meta name="robots" content="index,follow">\r
<meta name="title" content="AWStats Documentation - Glossary">\r
<title>AWStats Documentation - Glossary</title>\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="description" content="AWStats Documentation - License description">
-<meta name="keywords" content="awstats, awstat, license, permissions, agreements, allow, rights, GNU, GPL, general, public, license">
-<meta name="robots" content="index,follow">
-<meta name="title" content="AWStats Documentation - License description">
-<title>AWStats Documentation - License description</title>
-<link rel="stylesheet" href="styles.css" type="text/css">
-</head>
-
-<body topmargin=10 leftmargin=5>
-<!-- $Revision$ - $Author$ - $Date$ -->
-
-
-<table style="font: 10pt arial,helvetica,verdana" cellpadding=0 cellspacing=0 border=0 bgcolor=#FFFFFF width=100%>
-
-<!-- Large -->
-<tr style="font: 10pt arial,helvetica,verdana">
-<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>
-<td bgcolor=#9999cc align=center>
-<br>
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>
-<br>
-</td>
-<td bgcolor=#9999cc align=center>
-
-</td>
-</tr>
-
-</table>
-
-<br><br><H1 style="font: 26px Times;">AWStats License / Copyright</H1>
-
-<br>
-AWStats is distributed under the <a href="http://www.gnu.org/copyleft/gpl.html" target=_gnugpl>GNU General Public License (GPL)</a>.<br>
-So you must follow the line "Free software - Copylefted - GPL" to know what are major license agreements with AWStats.<br>
-<br>
-
-<hr>
-<br>
-
-<img src="images/license_chart.png"><br>
-<br>
-
-<hr>
-
-<script language=javascript>
- var lastmod = new Date(document.lastModified);
- if (lastmod.getDate() > 0) {
- if (lastmod.getDate()<10) zerod="0"
- else zerod="";
- if (lastmod.getMonth()<9) zerom="0"
- else zerom=""
- year2kok=lastmod.getYear();
- if (year2kok<100) year2kok+=2000;
- if ((year2kok>=100) && (year2kok < 1970)) year2kok+=1900;
- document.writeln("Last revision: "+year2kok+"-"+zerom+(lastmod.getMonth()+1)+"-"+zerod+lastmod.getDate());
- }
-</script>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">\r
+<html>\r
+<head>\r
+<meta name="description" content="AWStats Documentation - License description">\r
+<meta name="keywords" content="awstats, awstat, license, permissions, agreements, allow, rights, GNU, GPL, general, public, license">\r
+<meta name="robots" content="index,follow">\r
+<meta name="title" content="AWStats Documentation - License description">\r
+<title>AWStats Documentation - License description</title>\r
+<link rel="stylesheet" href="styles.css" type="text/css">\r
+<!-- $Revision$ - $Author$ - $Date$ -->\r
+</head>\r
+\r
+<body topmargin=10 leftmargin=5>\r
+\r
+\r
+<table style="font: 10pt arial,helvetica,verdana" cellpadding=0 cellspacing=0 border=0 bgcolor=#FFFFFF width=100%>\r
+\r
+<!-- Large -->\r
+<tr style="font: 10pt arial,helvetica,verdana">\r
+<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
+<td bgcolor=#9999cc align=center>\r
+<br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
+<br>\r
+</td>\r
+<td bgcolor=#9999cc align=center>\r
+ \r
+</td>\r
+</tr>\r
+\r
+</table>\r
+\r
+<br><br><H1 style="font: 26px Times;">AWStats License / Copyright</H1>\r
+\r
+<br>\r
+AWStats is distributed under the <a href="http://www.gnu.org/copyleft/gpl.html" target=_gnugpl>GNU General Public License (GPL)</a>.<br>\r
+So you must follow the line "Free software - Copylefted - GPL" to know what are major license agreements with AWStats.<br>\r
+<br>\r
+\r
+<hr>\r
+<br>\r
+\r
+<img src="images/license_chart.png"><br>\r
+<br>\r
+\r
+<hr>\r
+\r
+<script language=javascript>\r
+ var lastmod = new Date(document.lastModified);\r
+ if (lastmod.getDate() > 0) {\r
+ if (lastmod.getDate()<10) zerod="0"\r
+ else zerod="";\r
+ if (lastmod.getMonth()<9) zerom="0"\r
+ else zerom=""\r
+ year2kok=lastmod.getYear();\r
+ if (year2kok<100) year2kok+=2000;\r
+ if ((year2kok>=100) && (year2kok < 1970)) year2kok+=1900;\r
+ document.writeln("Last revision: "+year2kok+"-"+zerom+(lastmod.getMonth()+1)+"-"+zerod+lastmod.getDate());\r
+ }\r
+</script>\r
+\r
+</body>\r
+</html>\r
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="description" content="AWStats Documentation - Security page">
-<meta name="keywords" content="awstats, awstat, security, tips">
-<meta name="robots" content="index,follow">
-<meta name="title" content="AWStats Documentation - Security page">
-<title>AWStats Documentation - Security page</title>
-<link rel="stylesheet" href="styles.css" type="text/css">
-</head>
-
-<body topmargin=10 leftmargin=5>
-<!-- $Revision$ - $Author$ - $Date$ -->
-
-
-<table style="font: 10pt arial,helvetica,verdana" cellpadding=0 cellspacing=0 border=0 bgcolor=#FFFFFF width=100%>
-
-<!-- Large -->
-<tr style="font: 10pt arial,helvetica,verdana">
-<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>
-<td bgcolor=#9999cc align=center>
-<br>
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>
-<br>
-</td>
-<td bgcolor=#9999cc align=center>
-
-</td>
-</tr>
-
-</table>
-
-
-<br><br><H1 style="font: 26px Times;">Little Tips about Security</H1>
-
-<br>
-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).<br>
-<br><br>
-This is example of possible way of working:<br>
-<br><br>
-
-<br><a name="1"><H2 style="font: 22px Times; color: #606060"><u>1) HIGHLY SECURED POLICY</u></H2></a><br>
-<font color=blue><b>Policy</b></font>:<br>
-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.<br>
-This is a very good choice for web hosting providers with few but very large web sites of important customers.<br>
-<font color=blue><b>Advantage</b></font>:<br>
-Very highly secured.<br>
-<font color=blue><b>Disadvantage</b></font>:<br>
-Statistics are static, no dynamic update/view.<br>
-<font color=blue><b>How</b></font>:<br>
-All statistics pages for a config/domain file are built in static html files using <b>-output -staticlinks</b> option.<br>
-There is no CGI use of AWStats and static built pages are stored in a web protected <b>realm</b> to
-be securely viewed by correct allowed users only (or sent by mails).<br>
-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 <i>user1</i> (or an admin user) and NO read and NO write permissions for any other users.<br>
-Then, check that the <b>SaveDatabaseFilesWithPermissionsForEveryone</b> parameter is set 0 in your config/domain files.<br>
-If AWStats database files for config/domain1 are read protected, only allowed users can see statistics for config/domain1.<br>
-If AWStats database files for config/domain1 are write protected, only allowed users can update statistics for config/domain1.<br>
-<br><br>
-
-<!--
-<br><a name="2"><H2 style="font: 22px Times; color: #606060"><u>2) HIGHLY SECURED POLICY</u></H2></a><br>
-<font color=blue><b>Policy</b></font>:<br>
-You have several different domains owned by different users and you want each owner of a domain
-to be able to see only his/her domain and to be able to update his/her statistics dynamically.<br>
-This might be a good choice for web hosting providers with several small private or public customers.<br>
-<font color=blue><b>Advantage</b></font>:<br>
-Statistics view is dynamic. A site owner can view its statistics dynamically. Update can also
-be made (if allowed) on-line.<br>
-<font color=blue><b>Disadvantage</b></font>:<br>
-No way to have 2 configurations files for 1 particular domain.<br>
-<font color=blue><b>How</b></font>:<br>
-First, AWStats must be placed in its own cgi-bin-awstats directory with no way for users to
-put in it a hacked version of AWStats (an unwritable directory).<br>
-Then, you must add an environment variable called <b>AWSTATS_CONFIG</b> in the web server environment
-for each domain to say which config file to use for a particular domain.<br>
-<u>With Apache web server, you must use the '<i>SetEnv</i>' directive. This is an example:</u><br><i>
-<VirtualHost www.xxx.yyy.zzz><br>
- ServerAdmin webmaster@mydomain.com<br>
- ServerName mydomain.com<br>
- ScriptAlias /cgi-bin-awstats/<br>
- DocumentRoot /usr/local/apache/html<br>
- SetEnv AWSTATS_CONFIG myconfigvalueformydomain<br>
-</VirtualHost><br>
-</i>
-When using AWStats as a CGI with the following URL '<i>http://mydomain.com/cgi-bin-awstats/awstats.pl</i>', AWStats
-will use the config file called <i>awstats.myconfigvalueformydomain.conf</i> to choose which statistics used,
-even if a visitor try to force the config/domain file with the URL '<i>http://mydomain.com/cgi-bin-awstats/awstats.pl?config=xxx</i>'.<br>
-<br><br>
--->
-
-<br><a name="2"><H2 style="font: 22px Times; color: #606060"><u>2) MEDIUM SECURED POLICY</u></H2></a><br>
-<font color=blue><b>Policy</b></font>:<br>
-You have several config/domain and several users. You want to specify which user can see or update dynamically
-statistics for each config/domain.<br>
-This is one of the most popular way of working.<br>
-<font color=blue><b>Advantage</b></font>:<br>
-Statistics are dynamic. High level of manageability.<br>
-<font color=blue><b>Disadvantage</b></font>:<br>
-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.<br>
-<font color=blue><b>How</b></font>:<br>
-awstats.pl file must be saved in a web protected <b>realm</b> to force a visitor to enter its username/password
-to access AWStats CGI program.<br>
-<u>Example of directives you can add into Apache to have awstats.pl in a web protected realm:</u><br>
-<i>
-<Files "awstats.pl"><br>
-AuthUserFile /path/to/.passwd<br>
-AuthGroupFile /path/to/.group<br>
-AuthName "Restricted Area For Customers"<br>
-AuthType Basic<br>
-require valid-user<br>
-</Files>
-</i><br>
-Then edit each config/domain file you want to be protected to set <b>AllowAccessFromWebToAuthenticatedUsersOnly</b> to 1.<br>
-You can also edit list of authorized users in the <b>AllowAccessFromWebToFollowingAuthenticatedUsers</b> parameter.<br>
-<br>
-Other tip: If you define <b>AWSTATS_CONFIG</b> environment variable in your web server environment (Adding
-<i>SetEnv AWSTATS_CONFIG myconfigvalueformydomain</i> with other directives in your Apache VirtualHost config), AWStats
-will use the config file called <i>awstats.myconfigvalueformydomain.conf</i> to choose which statistics used,
-even if a visitor try to force the config/domain file with the URL '<i>http://mydomain.com/cgi-bin-awstats/awstats.pl?config=xxx</i>'.
-This can be usefull for thoose who edit their config/domain file with <i>AllowAccessFromWebToFollowingAuthenticatedUsers="__REMOTE_USER__"</i>.<br>
-<br><br>
-
-<br><a name="3"><H2 style="font: 22px Times; color: #606060"><u>3) NO SECURITY POLICY</u></H2></a><br>
-<font color=blue><b>Policy</b></font>:<br>
-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.<br>
-<font color=blue><b>Advantage</b></font>:<br>
-Setup is very easy (No need of particular setup). Statistics are dynamic.<br>
-<font color=blue><b>Disadvantage</b></font>:<br>
-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.<br>
-<font color=blue><b>How</b></font>:<br>
-No particular things to do.<br>
-<br>
-<br>
-<br>
-
-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...<br>
-<br>
-
-
-<br>
-<hr>
-
-<script language=javascript>
- var lastmod = new Date(document.lastModified);
- if (lastmod.getDate() > 0) {
- if (lastmod.getDate()<10) zerod="0"
- else zerod="";
- if (lastmod.getMonth()<9) zerom="0"
- else zerom=""
- year2kok=lastmod.getYear();
- if (year2kok<100) year2kok+=2000;
- if ((year2kok>=100) && (year2kok < 1970)) year2kok+=1900;
- document.writeln("Last revision: "+year2kok+"-"+zerom+(lastmod.getMonth()+1)+"-"+zerod+lastmod.getDate());
- }
-</script>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">\r
+<html>\r
+<head>\r
+<meta name="description" content="AWStats Documentation - Security page">\r
+<meta name="keywords" content="awstats, awstat, security, tips">\r
+<meta name="robots" content="index,follow">\r
+<meta name="title" content="AWStats Documentation - Security page">\r
+<title>AWStats Documentation - Security page</title>\r
+<link rel="stylesheet" href="styles.css" type="text/css">\r
+<!-- $Revision$ - $Author$ - $Date$ -->\r
+</head>\r
+\r
+<body topmargin=10 leftmargin=5>\r
+\r
+\r
+<table style="font: 10pt arial,helvetica,verdana" cellpadding=0 cellspacing=0 border=0 bgcolor=#FFFFFF width=100%>\r
+\r
+<!-- Large -->\r
+<tr style="font: 10pt arial,helvetica,verdana">\r
+<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
+<td bgcolor=#9999cc align=center>\r
+<br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
+<br>\r
+</td>\r
+<td bgcolor=#9999cc align=center>\r
+ \r
+</td>\r
+</tr>\r
+\r
+</table>\r
+\r
+\r
+<br><br><H1 style="font: 26px Times;">Little Tips about Security</H1>\r
+\r
+<br>\r
+A lot of AWStats users have several web site to manage. This is particularly true for web hosting providers.\r
+The most common things you would like to do is to prevent user xxx (having a site www.xxx.com) to see\r
+statistics of user yyy (having a site www.yyy.com).<br>\r
+<br><br>\r
+This is example of possible way of working:<br>\r
+<br><br>\r
+\r
+<br><a name="1"><H2 style="font: 22px Times; color: #606060"><u>1) HIGHLY SECURED POLICY</u></H2></a><br>\r
+<font color=blue><b>Policy</b></font>:<br>\r
+You have several different config/domains owned by different users and you want to build statistics for each\r
+of them. You don't need that your customer have "real-time" statistics.<br>\r
+This is a very good choice for web hosting providers with few but very large web sites of important customers.<br>\r
+<font color=blue><b>Advantage</b></font>:<br>\r
+Very highly secured.<br>\r
+<font color=blue><b>Disadvantage</b></font>:<br>\r
+Statistics are static, no dynamic update/view.<br>\r
+<font color=blue><b>How</b></font>:<br>\r
+All statistics pages for a config/domain file are built in static html files using <b>-output -staticlinks</b> option.<br>\r
+There is no CGI use of AWStats and static built pages are stored in a web protected <b>realm</b> to\r
+be securely viewed by correct allowed users only (or sent by mails).<br>\r
+If users have a command line access (telnet) on statistics server, you must set correct permissions on AWStats\r
+database files. Set all AWStats database files (built by the update process) for config/domain1 to have read/write\r
+for <i>user1</i> (or an admin user) and NO read and NO write permissions for any other users.<br>\r
+Then, check that the "<a href="awstats_config.html#SaveDatabaseFilesWithPermissionsForEveryone">SaveDatabaseFilesWithPermissionsForEveryone</a>" parameter is set 0 in your config/domain files.<br>\r
+If AWStats database files for config/domain1 are read protected, only allowed users can see statistics for config/domain1.<br>\r
+If AWStats database files for config/domain1 are write protected, only allowed users can update statistics for config/domain1.<br>\r
+<br><br>\r
+\r
+<!--\r
+<br><a name="2"><H2 style="font: 22px Times; color: #606060"><u>2) HIGHLY SECURED POLICY</u></H2></a><br>\r
+<font color=blue><b>Policy</b></font>:<br>\r
+You have several different domains owned by different users and you want each owner of a domain\r
+to be able to see only his/her domain and to be able to update his/her statistics dynamically.<br>\r
+This might be a good choice for web hosting providers with several small private or public customers.<br>\r
+<font color=blue><b>Advantage</b></font>:<br>\r
+Statistics view is dynamic. A site owner can view its statistics dynamically. Update can also\r
+be made (if allowed) on-line.<br>\r
+<font color=blue><b>Disadvantage</b></font>:<br>\r
+No way to have 2 configurations files for 1 particular domain.<br>\r
+<font color=blue><b>How</b></font>:<br>\r
+First, AWStats must be placed in its own cgi-bin-awstats directory with no way for users to\r
+put in it a hacked version of AWStats (an unwritable directory).<br>\r
+Then, you must add an environment variable called <b>AWSTATS_CONFIG</b> in the web server environment\r
+for each domain to say which config file to use for a particular domain.<br>\r
+<u>With Apache web server, you must use the '<i>SetEnv</i>' directive. This is an example:</u><br><i>\r
+<VirtualHost www.xxx.yyy.zzz><br>\r
+ ServerAdmin webmaster@mydomain.com<br>\r
+ ServerName mydomain.com<br>\r
+ ScriptAlias /cgi-bin-awstats/<br>\r
+ DocumentRoot /usr/local/apache/html<br>\r
+ SetEnv AWSTATS_CONFIG myconfigvalueformydomain<br>\r
+</VirtualHost><br>\r
+</i>\r
+When using AWStats as a CGI with the following URL '<i>http://mydomain.com/cgi-bin-awstats/awstats.pl</i>', AWStats\r
+will use the config file called <i>awstats.myconfigvalueformydomain.conf</i> to choose which statistics used,\r
+even if a visitor try to force the config/domain file with the URL '<i>http://mydomain.com/cgi-bin-awstats/awstats.pl?config=xxx</i>'.<br>\r
+<br><br>\r
+-->\r
+\r
+<br><a name="2"><H2 style="font: 22px Times; color: #606060"><u>2) MEDIUM SECURED POLICY</u></H2></a><br>\r
+<font color=blue><b>Policy</b></font>:<br>\r
+You have several config/domain and several users. You want to specify which user can see or update dynamically\r
+statistics for each config/domain.<br>\r
+This is one of the most popular way of working.<br>\r
+<font color=blue><b>Advantage</b></font>:<br>\r
+Statistics are dynamic. High level of manageability.<br>\r
+<font color=blue><b>Disadvantage</b></font>:<br>\r
+AWStats database files must still be readable by anonymous web server user, so if an experimented user can have an access to\r
+the server (telnet) where AWStats database files are stored, he can succeed in installing and running a "hacked" version\r
+of AWStats that ignores value of parameter AllowAccessFromWebToAuthenticatedUsersOnly.<br>\r
+<font color=blue><b>How</b></font>:<br>\r
+awstats.pl file must be saved in a web protected <b>realm</b> to force a visitor to enter its username/password\r
+to access AWStats CGI program.<br>\r
+<u>Example of directives you can add into Apache to have awstats.pl in a web protected realm:</u><br>\r
+<i>\r
+<Files "awstats.pl"><br>\r
+AuthUserFile /path/to/.passwd<br>\r
+AuthGroupFile /path/to/.group<br>\r
+AuthName "Restricted Area For Customers"<br>\r
+AuthType Basic<br>\r
+require valid-user<br>\r
+</Files>\r
+</i><br>\r
+Then edit each config/domain file you want to be protected to set "<a href="awstats_config.html#AllowAccessFromWebToAuthenticatedUsersOnly">AllowAccessFromWebToAuthenticatedUsersOnly</a>" to 1.<br>\r
+You can also edit list of authorized users in the "<a href="awstats_config.html#AllowAccessFromWebToFollowingAuthenticatedUsers">AllowAccessFromWebToFollowingAuthenticatedUsers</a>" parameter.<br>\r
+<br>\r
+Other tip: If you define <b>AWSTATS_CONFIG</b> environment variable in your web server environment (Adding\r
+<i>SetEnv AWSTATS_CONFIG myconfigvalueformydomain</i> with other directives in your Apache VirtualHost config), AWStats\r
+will use the config file called <i>awstats.myconfigvalueformydomain.conf</i> to choose which statistics used,\r
+even if a visitor try to force the config/domain file with the URL '<i>http://mydomain.com/cgi-bin-awstats/awstats.pl?config=xxx</i>'.\r
+This can be usefull for thoose who edit their config/domain file with <a href="awstats_config.html#AllowAccessFromWebToFollowingAuthenticatedUsers">AllowAccessFromWebToFollowingAuthenticatedUsers</a>="__REMOTE_USER__"</i>.<br>\r
+<br><br>\r
+\r
+<br><a name="3"><H2 style="font: 22px Times; color: #606060"><u>3) NO SECURITY POLICY</u></H2></a><br>\r
+<font color=blue><b>Policy</b></font>:<br>\r
+You have only one hosts or several hosts or users but you don't need to manage particular permissions\r
+for your different config/domain statistics.<br>\r
+<font color=blue><b>Advantage</b></font>:<br>\r
+Setup is very easy (No need of particular setup). Statistics are dynamic.<br>\r
+<font color=blue><b>Disadvantage</b></font>:<br>\r
+No way to prevent stats for config/domain to be seen by a user that known the\r
+config/domain name and the url syntax to see stats of a particular config/domain.<br>\r
+<font color=blue><b>How</b></font>:<br>\r
+No particular things to do.<br>\r
+<br>\r
+<br>\r
+<br>\r
+\r
+There is a lot of possible use for AWStats combining all its options/parameter with all web servers options/parameters.\r
+Just use the one you need...<br>\r
+<br>\r
+\r
+\r
+<br>\r
+<hr>\r
+\r
+<script language=javascript>\r
+ var lastmod = new Date(document.lastModified);\r
+ if (lastmod.getDate() > 0) {\r
+ if (lastmod.getDate()<10) zerod="0"\r
+ else zerod="";\r
+ if (lastmod.getMonth()<9) zerom="0"\r
+ else zerom=""\r
+ year2kok=lastmod.getYear();\r
+ if (year2kok<100) year2kok+=2000;\r
+ if ((year2kok>=100) && (year2kok < 1970)) year2kok+=1900;\r
+ document.writeln("Last revision: "+year2kok+"-"+zerom+(lastmod.getMonth()+1)+"-"+zerod+lastmod.getDate());\r
+ }\r
+</script>\r
+\r
+</body>\r
+</html>\r
<meta name="title" content="AWStats Documentation - Setup page">\r
<title>AWStats Documentation - Setup page</title>\r
<link rel="stylesheet" href="styles.css" type="text/css">\r
+<!-- $Revision$ - $Author$ - $Date$ -->\r
</head>\r
\r
<body topmargin=10 leftmargin=5>\r
-<!-- $Revision$ - $Author$ - $Date$ -->\r
\r
\r
<table style="font: 10pt arial,helvetica,verdana" cellpadding=0 cellspacing=0 border=0 bgcolor=#FFFFFF width=100%>\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
<i>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)"</i><br>\r
<br>\r
* Copy all the content of provided AWStats cgi-bin directory into your web \r
-server cgi-bin directory (this includes <b>awstats.pl</b>, <b>awstats.model.conf</b>, and the <b>lang</b> and <b>db</b> sub-directories).<br>\r
+server cgi-bin directory (this includes <b>awstats.pl</b>, <b>awstats.model.conf</b>, and the <b>lang</b> and <b>lib</b> sub-directories).<br>\r
<br>\r
* If necessary (should not with most perl interpreter), in awstats.pl file, edit the first line<br>\r
<i>#!/usr/bin/perl</i><br>\r
- /etc/opt/awstats or /etc/awstats or /etc or same directory than awstats.pl (so cgi-bin) for Unix/Linux users.<br>\r
- same directory than awstats.pl (so cgi-bin) for Windows and other OS.<br>\r
Edit this new config file with your own setup :<br>\r
-- Change <b>"LogFile"</b> value with full path of your web server log file (You\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
-- Check if <b>"LogFormat"</b> has the value "1" (it means "NCSA apache combined/ELF/XLF log format").<br>\r
-- Change <b>"DirIcons"</b> parameter to reflect relative URL of icon directory.<br>\r
-- Edit <b>"SiteDomain"</b> parameter with the main domain name or the intranet \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 URL of icon directory.<br>\r
+- Edit "<a href="awstats_config.html#SiteDomain">SiteDomain</a>" parameter with the main domain name or the intranet \r
web server name used to reach the web site to analyze.<br>\r
- You can change other parameters if you want.<br>\r
<br>\r
<i>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</i>\r
<br>\r
* Copy all the content of provided AWStats cgi-bin directory into your web \r
-server cgi-bin directory (this includes <b>awstats.pl</b>, <b>awstats.model.conf</b>, and the <b>lang</b> and <b>db</b> sub-directories).<br>\r
+server cgi-bin directory (this includes <b>awstats.pl</b>, <b>awstats.model.conf</b>, and the <b>lang</b> and <b>lib</b> sub-directories).<br>\r
<br> \r
* Move all AWStats <b>icon sub-directories</b> into a directory readable by your\r
web server, for example C:\yourwwwroot\icon.<br>\r
Whatever the name you choose, this new file must be stored in<br>\r
- same directory than awstats.pl (so cgi-bin)<br>\r
Edit this new config file with your own setup :<br>\r
-- Change <b>"LogFile"</b> value with full path of your web server log file (You\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 <b>"LogFormat"</b> to value "2" (it means "IIS Extended W3C log format").<br>\r
-- Change <b>"DirIcons"</b> parameter to reflect relative URL of icon directory.<br>\r
-- Edit <b>"SiteDomain"</b> parameter with the main domain name or the intranet\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 URL of icon directory.<br>\r
+- Edit "<a href="awstats_config.html#SiteDomain">SiteDomain</a>" parameter with the main domain name or the intranet\r
web server name used to reach the web site to analyze.<br>\r
- You can change other parameters if you want.<br>\r
<br>\r
<b>3) With other web servers</b><br>\r
<br>\r
Setup process is similar to setup for Apache or IIS.<br>\r
-Use <b>"LogFormat"</b> to value "3" if you have WebStar native log format.<br>\r
+Use "<a href="awstats_config.html#LogFormat">LogFormat</a>" to value "3" if you have WebStar native log format.<br>\r
<br>\r
\r
\r
<br>\r
Even if AWStats allows "real-time" statistics with its "update from browser feature" (See next\r
section <a href="#READ">Read Statistics</a>), you must run the update process from a scheduler frequently.<br>\r
-The first update of statistics can be made the first time manually from the command line (the first time,\r
+* The first update of statistics can be made the first time manually from the command line (the first time,\r
process may be long :<br>\r
<b><i>awstats.pl -config=virtualhostname -update</i></b><br>\r
<br>\r
Found 225601 new records.<br>\r
</i><br>\r
<b>Dropped records</b> are records discarded because they were not user HTTP request or requests were not qualified\r
-by AWStats filters (See <a href="awstats_config.html#SkipHosts">SkipHosts</a>, <a href="awstats_config.html#SkipFiles">SkipFiles</a>,\r
-and <a href="awstats_config.html#OnlyFiles">OnlyFiles</a> parameters).\r
+by AWStats filters (See "<a href="awstats_config.html#SkipHosts">SkipHosts</a>", "<a href="awstats_config.html#SkipFiles">SkipFiles</a>",\r
+and "<a href="awstats_config.html#OnlyFiles">OnlyFiles</a>" parameters).\r
If you want to see which lines were dropped, you can add the <b>-showdropped</b> option on command line.<br>\r
<b>Corrupted records</b> are records that does not match log format defined by "LogFormat" parameter in AWStats config/domain file.\r
With all webservers you can experience a little bit corrupted records (<5%) even when everythings work correctly.\r
This can be the result of several reasons: Web server internal bugs, bad requests made by buggy browsers, web server brutal stop...<br>\r
-If all your lines are corrupted and "LogFormat" parameter in AWStats config/domain file is correct, may be it's the log\r
+If all your lines are corrupted and "LogFormat" parameter in AWStats config/domain file is correct, it may be the log\r
format setup in your web server that is wrong. Don't forget that you "LogFormat" parameter in AWStats config/domain\r
file MUST match the log file format you analyze.<br>\r
If you want to see which lines are corrupted, you can add the <b>-showcorrupted</b> option on command line.<br>\r
<br>\r
Note : A log analysis process is slow (one second for each 4100 lines of your\r
logfile with Athlon 1Ghz, plus DNS resolution time for each different IP\r
-address in your logfile if <b>"DNSLookup"</b> is set to 1 and not already done in your log file).<br>\r
+address in your logfile if "<a href="awstats_config.html#DNSLookup">DNSLookup</a>" is set to 1 and not already done in your log file).<br>\r
See <a href="awstats_benchmark.html">Benchmark page</a> for more accurate information.<br>\r
<br>\r
\r
<br>\r
-New updates should be made from an automatic process.<br>\r
+* Then new updates should be made from an automatic process.<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
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 <b>"PurgeLogFile"</b> parameter,\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. 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
<br>\r
\r
* You can build the main report, in a static HTML page, from the command line, like this :<br>\r
-<b><i>awstats.pl -config=virtualhostname -output -staticlinks > awstats.mainresults.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output -staticlinks > awstats.virtualhostname.html</i></b><br>\r
<br>\r
You can also use all other output options (each of them give you another report).\r
This is how to use all other possible output options:<br>\r
-<b><i>awstats.pl -config=virtualhostname -output=allhosts -staticlinks > awstats.allhosts.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=lasthosts -staticlinks > awstats.lasthosts.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=unknownip -staticlinks > awstats.unknownip.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=urldetail -staticlinks > awstats.urldetail.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=urldetail:</b>filter<b> -staticlinks > awstats.urldetailfiltered.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=unknownos -staticlinks > awstats.unknownos.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=unknownbrowsers -staticlinks > awstats.unknownbrowsers.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=browserdetail -staticlinks > awstats.browserdetail.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=allkeyphrases -staticlinks > awstats.allkeyphrases.html</i></b><br>\r
-<b><i>awstats.pl -config=virtualhostname -output=errors404 -staticlinks > awstats.errors404.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=allhosts -staticlinks > awstats.virtualhostname.allhosts.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=lasthosts -staticlinks > awstats.virtualhostname.lasthosts.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=unknownip -staticlinks > awstats.virtualhostname.unknownip.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=urldetail -staticlinks > awstats.virtualhostname.urldetail.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=urldetail:</b>filter<b> -staticlinks > awstats.virtualhostname.urldetailfiltered.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=unknownos -staticlinks > awstats.virtualhostname.unknownos.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=unknownbrowsers -staticlinks > awstats.virtualhostname.unknownbrowsers.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=browserdetail -staticlinks > awstats.virtualhostname.browserdetail.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=allkeyphrases -staticlinks > awstats.virtualhostname.allkeyphrases.html</i></b><br>\r
+<b><i>awstats.pl -config=virtualhostname -output=errors404 -staticlinks > awstats.virtualhostname.errors404.html</i></b><br>\r
+<br>\r
+Note: If you prefer, you can use <a href="awstats_tools.html#awstats_buildstaticpages">awstats_buildstaticpages</a> tool to build all those\r
+pages in one command.<br>\r
<br>\r
* You can also view dynamically your statistics from a browser.<br>\r
-If you named your config file awstats.virtualhostname.conf, use URL:<br>\r
+If you named your config file awstats.<i>virtualhostname</i>.conf, use URL:<br>\r
<b><i>http://www.myserver.mydomain/cgi-bin/awstats.pl?config=virtualhostname</i></b><br>\r
-where virtualhostname is used to know which config file to use (AWStats\r
-will use awstats.virtualhostname.conf file).<br>\r
+where <i>virtualhostname</i> is used to know which config file to use (AWStats\r
+will use awstats.<i>virtualhostname</i>.conf file).<br>\r
If you named your config file awstats.conf, just use URL:<br>\r
<b><i>http://www.myserver.mydomain/cgi-bin/awstats.pl</i></b><br>\r
<br>\r
-Note: If <b>"AllowToUpdateStatsFromBrowser"</b> parameter is set to 1 in AWStats config/domain file,\r
+Note: If "<a href="awstats_config.html#AllowToUpdateStatsFromBrowser">AllowToUpdateStatsFromBrowser</a>" parameter is set to 1 in AWStats config/domain file,\r
you will also be able to run the update process from your browser. Just click on link "Update now".<br>\r
<br><br>\r
\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
\r
<br>\r
This is a list of other tools provided with AWStats.<br>\r
+All those tools are available in <b>tools</b> directory of AWStats distribution.<br>\r
<br><br>\r
\r
<br><a name="awstats_buildstaticpages"><H2 style="font: 22px Times; color: #606060"><u>awstats_buildstaticpages</u></H2></a>\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>\r
<td bgcolor=#9999cc align=center>\r
<br>\r
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>\r
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>\r
<br>\r
</td>\r
<td bgcolor=#9999cc align=center>\r
<td bgcolor=#9999cc align=center><a href="/"><img src="images/awstats_logo4.png" border=0></a></td>
<td bgcolor=#9999cc align=center>
<br>
-<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.0 Documentation</b></font><br>
+<font style="font: 16pt Times;" color=#EEEEFF><b>AWStats logfile analyzer 4.1 Documentation</b></font><br>
<br>
</td>
<td bgcolor=#9999cc align=center>
projects / thirdparty / AWStats.git / commitdiff
