<html>
<head>
<meta name="description" content="AWStats Documentation - Setup page">
- <meta name="keywords"\r
- content="awstats, awstat, setup, config, install">\r
+ <meta name="keywords"
+ content="awstats, awstat, setup, config, install">
<meta name="robots" content="index,follow">
<meta name="title" content="AWStats Documentation - Setup page">
<title>AWStats Documentation - Setup page</title>
<link rel="stylesheet" href="styles.css" type="text/css">
<!-- $Revision$ - $Author$ - $Date$ -->
</head>
-<body topmargin="10" leftmargin="5">\r
-<table\r
- style="font-family: arial,helvetica,verdana; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"\r
- bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0"\r
- width="100%">\r
-<!-- Large --> <tbody>\r
- <tr\r
- style="font-family: arial,helvetica,verdana; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">\r
- <td align="center" bgcolor="#9999cc"><a href="/"><img\r
- src="images/awstats_logo4.png" border="0"></a></td>\r
- <td align="center" bgcolor="#9999cc"> <br>\r
- <font\r
- style="font-family: arial,helvetica,sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 16pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"\r
- color="#eeeeff"><b>AWStats logfile analyzer 6.5 Documentation</b></font><br>\r
+<body topmargin="10" leftmargin="5">
+<table
+ style="font-family: arial,helvetica,verdana; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"
+ bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0"
+ width="100%">
+<!-- Large --> <tbody>
+ <tr
+ style="font-family: arial,helvetica,verdana; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
+ <td align="center" bgcolor="#9999cc"><a href="/"><img
+ src="images/awstats_logo4.png" border="0"></a></td>
+ <td align="center" bgcolor="#9999cc"> <br>
+ <font
+ style="font-family: arial,helvetica,sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 16pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"
+ color="#eeeeff"><b>AWStats logfile analyzer 6.5 Documentation</b></font><br>
<br>
</td>
- <td align="center" bgcolor="#9999cc"> </td>\r
+ <td align="center" bgcolor="#9999cc"> </td>
</tr>
- </tbody>\r
+ </tbody>
</table>
-<br>\r
-<br>\r
-<h1\r
- style="font-family: arial,helvetica,sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 26px; line-height: normal; font-size-adjust: none; font-stretch: normal;">AWStats\r
-Installation, Configuration and Reporting</h1>\r
-There are 3 steps to begin using AWStats:<br>\r
+<br>
+<br>
+<h1
+ style="font-family: arial,helvetica,sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 26px; line-height: normal; font-size-adjust: none; font-stretch: normal;">AWStats
+Installation, Configuration and Reporting</h1>
+There are 3 steps to begin using AWStats:<br>
<ul>
- <li><a href="#INSTALL">I. Setup: Installation and configuration</a><br>\r
- </li>\r
- <li><a href="#BUILD_UPDATE">II. Process logs: Building/updating\r
-statistics database</a><br>\r
- </li>\r
- <li><a href="#READ">III. Run Reports: Building and reading reports</a><br>\r
- </li>\r
+ <li><a href="#INSTALL">I. Setup: Installation and configuration</a><br>
+ </li>
+ <li><a href="#BUILD_UPDATE">II. Process logs: Building/updating
+statistics database</a><br>
+ </li>
+ <li><a href="#READ">III. Run Reports: Building and reading reports</a><br>
+ </li>
</ul>
<br>
If not, you can install a recent Perl interpreter from <a href="http://www.activestate.com/ActivePerl/">ActivePerl</a> (<font color=#221188>Win32</font>) or <a href="http://www.perl.com/pub/language/info/software.html">Perl.com</a> (<font color=#221188>Unix/Linux/Other</font>).<br>
-->
<br>
-<a name="INSTALL">\r
-<h2 style=""><u>I. Setup: Installation and configuration using\r
-awstats_configure.pl</u></h2>\r
-</a><br>\r
-<a name="INSTALLAPACHE"><b>A) Setup for an Apache or compatible web\r
-server (on Unix/Linux, Windows, MacOS...)</b></a><br>\r
-<br>\r
-<font style="color: rgb(17, 17, 85);"><b>* Step 1</b>:</font><br>\r
-<br>\r
-(if you use a package provided with a Linux distribution or Windows\r
-installer, step 1\r
-might have already been done; if you don't know, you can run this step\r
-again)<br>\r
-<br>
-After downloading and extracting the AWStats package, you should run\r
-the awstats_configure.pl script to do\r
+<a name="INSTALL">
+<h2 style=""><u>I. Setup: Installation and configuration using
+awstats_configure.pl</u></h2>
+</a><br>
+<a name="INSTALLAPACHE"><b>A) Setup for an Apache or compatible web
+server (on Unix/Linux, Windows, MacOS...)</b></a><br>
+<br>
+<font style="color: rgb(17, 17, 85);"><b>* Step 1</b>:</font><br>
+<br>
+(if you use a package provided with a Linux distribution or Windows
+installer, step 1
+might have already been done; if you don't know, you can run this step
+again)<br>
+<br>
+After downloading and extracting the AWStats package, you should run
+the awstats_configure.pl script to do
several setup actions.
-You will find it in the AWStats <b>tools</b> directory (If using the\r
-Windows installer, the script is\r
+You will find it in the AWStats <b>tools</b> directory (If using the
+Windows installer, the script is
automatically launched):<br>
<table border=1 cellpadding=1 cellspacing=0 bgcolor=#F4F4F4 width="95%" class=CFAQ><tr class=CFAQ><td class=CFAQ>
perl awstats_configure.pl
</td></tr></table>
<br>
<ul>
- <u>This is what the script does/asks (you can do all these steps\r
-manually instead of running awstats_configure.pl if you prefer):</u><br>\r
+ <u>This is what the script does/asks (you can do all these steps
+manually instead of running awstats_configure.pl if you prefer):</u><br>
<br>
-A) awstats_configure.pl tries to determine your current log format from\r
-your Apache web server\r
-configuration file httpd.conf (it asks for the path if not found).\r
+A) awstats_configure.pl tries to determine your current log format from
+your Apache web server
+configuration file httpd.conf (it asks for the path if not found).
If you use a <b>common</b> log, awstats_configure.pl will
-suggest changing it to the <b>NCSA combined/XLF/ELF</b> format (you\r
-can use your own custom log\r
-format but this predefined log format is often the best choice and\r
-makes setup easier).<br>\r
-If you answer yes, awstats_configure.pl will modify your <b>httpd.conf</b>,\r
-changing the\r
-following directive:<br>\r
- <i>from<br>\r
-CustomLog /yourlogpath/yourlogfile common</i><br>\r
-to<br>\r
+suggest changing it to the <b>NCSA combined/XLF/ELF</b> format (you
+can use your own custom log
+format but this predefined log format is often the best choice and
+makes setup easier).<br>
+If you answer yes, awstats_configure.pl will modify your <b>httpd.conf</b>,
+changing the
+following directive:<br>
+ <i>from<br>
+CustomLog /yourlogpath/yourlogfile common</i><br>
+to<br>
<i>CustomLog /yourlogpath/yourlogfile combined</i><br>
<br>
-See the Apache manual for more information on this directive (possibly\r
-installed on your server as www.mysite.com/manual).<br>\r
- <br>\r
-B) awstats_configure.pl will then add, if not already present, the\r
-following directives to your Apache configuration file\r
-(note that the "/usr/local/awstats/wwwroot" path might differ according\r
-to your distribution or OS:<br>\r
- <i> <br>\r
-# <br>\r
-# Directives to add to your Apache conf file to allow use of AWStats as\r
-a CGI. <br>\r
-# Note that path "/usr/local/awstats/" must reflect your AWStats\r
-Installation path. <br>\r
-# <br>\r
-Alias /awstatsclasses "/usr/local/awstats/wwwroot/classes/" <br>\r
-Alias /awstatscss "/usr/local/awstats/wwwroot/css/" <br>\r
-Alias /awstatsicons "/usr/local/awstats/wwwroot/icon/" <br>\r
-ScriptAlias /awstats/ "/usr/local/awstats/wwwroot/cgi-bin/" <br>\r
-# <br>\r
-# This is to permit URL access to scripts/files in AWStats directory. <br>\r
-# <br>\r
-<Directory "/usr/local/awstats/wwwroot"> <br>\r
-Options None <br>\r
-AllowOverride None <br>\r
-Order allow,deny <br>\r
-Allow from all <br>\r
-</Directory> </i><br>\r
- <br>\r
-C) if changes were made as indicated in parts A and B,\r
-awstats_configure.pl restarts Apache to apply the changes. To be\r
-sure the log format change is effective, go to your homepage. This is\r
-an example of the type of records you should see inserted in your new\r
-log file after Apache\r
-was restarted:<br>\r
- <br>\r
-62.161.78.75 - - [dd/mmm/yyyy:hh:mm:ss +0000] "GET / HTTP/1.1" 200 1234\r
-"http://www.from.com/from.html" "Mozilla/4.0 (compatible; MSIE 5.01;\r
-Windows NT 5.0)"<br>\r
- <br>\r
-D) awstats_configure.pl will ask you for a name for the configuration\r
-profile file. Enter an appropriate name such as that of your\r
-web server or the virtual domain to be analyzed, i.e. <b\r
- style="font-style: italic;">mysite</b>.<br>\r
- <br>\r
-awstats_configure.pl will create a new file called <b>awstats.<span\r
- style="font-style: italic;">mysite</span>.conf</b>\r
-by copying the template file <b>awstats.model.conf</b>.\r
-The new file location is:<br>\r
+See the Apache manual for more information on this directive (possibly
+installed on your server as www.mysite.com/manual).<br>
+ <br>
+B) awstats_configure.pl will then add, if not already present, the
+following directives to your Apache configuration file
+(note that the "/usr/local/awstats/wwwroot" path might differ according
+to your distribution or OS:<br>
+ <i> <br>
+# <br>
+# Directives to add to your Apache conf file to allow use of AWStats as
+a CGI. <br>
+# Note that path "/usr/local/awstats/" must reflect your AWStats
+Installation path. <br>
+# <br>
+Alias /awstatsclasses "/usr/local/awstats/wwwroot/classes/" <br>
+Alias /awstatscss "/usr/local/awstats/wwwroot/css/" <br>
+Alias /awstatsicons "/usr/local/awstats/wwwroot/icon/" <br>
+ScriptAlias /awstats/ "/usr/local/awstats/wwwroot/cgi-bin/" <br>
+# <br>
+# This is to permit URL access to scripts/files in AWStats directory. <br>
+# <br>
+<Directory "/usr/local/awstats/wwwroot"> <br>
+Options None <br>
+AllowOverride None <br>
+Order allow,deny <br>
+Allow from all <br>
+</Directory> </i><br>
+ <br>
+C) if changes were made as indicated in parts A and B,
+awstats_configure.pl restarts Apache to apply the changes. To be
+sure the log format change is effective, go to your homepage. This is
+an example of the type of records you should see inserted in your new
+log file after Apache
+was restarted:<br>
+ <br>
+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)"<br>
+ <br>
+D) awstats_configure.pl will ask you for a name for the configuration
+profile file. Enter an appropriate name such as that of your
+web server or the virtual domain to be analyzed, i.e. <b
+ style="font-style: italic;">mysite</b>.<br>
+ <br>
+awstats_configure.pl will create a new file called <b>awstats.<span
+ style="font-style: italic;">mysite</span>.conf</b>
+by copying the template file <b>awstats.model.conf</b>.
+The new file location is:<br>
- For Linux/BSD/Unix users: /etc/awstats.<br>
-- For Mac OS X, Windows and other operating systems: the same directory\r
-as awstats.pl\r
-(cgi-bin).<br>\r
+- For Mac OS X, Windows and other operating systems: the same directory
+as awstats.pl
+(cgi-bin).<br>
<br>
E) awstats_configure.pl ends.<br>
<br>
</ul>
-<font style="color: rgb(17, 17, 85);"><b>* Step 2</b>:</font><br>\r
-<br>
-Once a configuration file has been created (by\r
-awstats_configure.pl, by your package\r
-installer or just by a manual copy of awstats.model.conf), it's\r
-important to verify that the "MAIN PARAMETERS"\r
-match your needs. Open awstats.<span\r
- style="font-style: italic; font-weight: bold;">mysite</span>.conf in\r
-your favorite text editor (i.e. notepad.exe, vi, gedit, etc) -\r
-don´t use a word processor - and make changes as required.<br>\r
-<br>\r
-Particular attention should be given to these parameters:<br>\r
-- Verify the <a href="awstats_config.html#LogFile">LogFile</a>\r
-value. It should be the full path of your server log file (You\r
-can also use a relative path from your awstats.pl directory, but a full\r
-path avoids errors).<br>\r
-- Verify the <a href="awstats_config.html#LogType">LogType</a>\r
-value. It should be "W" for analyzing\r
-web log files.<br>\r
-- Check if <a href="awstats_config.html#LogFormat">LogFormat</a> is\r
-set to "1" (for "NCSA apache combined/ELF/XLF log format")\r
-or use a custom log format if you don't use the combined log format.<br>\r
-- Set the <a href="awstats_config.html#SiteDomain">SiteDomain</a>\r
-parameter to the main domain name or the intranet web server name\r
-used to reach the web site to analyze (Example: www.mysite.com). If\r
-you have several\r
-possible names for same site, use the main domain name and add the\r
-others to the list in the <a href="awstats_config.html#HostAlias">HostAlias</a>\r
-parameter.<br>\r
-- You can also change other parameters if you want. The full list is\r
-described in <a href="awstats_config.html">Configurations/Directives\r
-options</a> page.<br>\r
-<br>\r
-Installation and configuration is finished. You can jump to the <a\r
- href="#BUILD_UPDATE">Process logs: Building/updating statistics\r
-database</a> section.<br>\r
+<font style="color: rgb(17, 17, 85);"><b>* Step 2</b>:</font><br>
+<br>
+Once a configuration file has been created (by
+awstats_configure.pl, by your package
+installer or just by a manual copy of awstats.model.conf), it's
+important to verify that the "MAIN PARAMETERS"
+match your needs. Open awstats.<span
+ style="font-style: italic; font-weight: bold;">mysite</span>.conf in
+your favorite text editor (i.e. notepad.exe, vi, gedit, etc) -
+don´t use a word processor - and make changes as required.<br>
+<br>
+Particular attention should be given to these parameters:<br>
+- Verify the <a href="awstats_config.html#LogFile">LogFile</a>
+value. It should be the full path of your server log file (You
+can also use a relative path from your awstats.pl directory, but a full
+path avoids errors).<br>
+- Verify the <a href="awstats_config.html#LogType">LogType</a>
+value. It should be "W" for analyzing
+web log files.<br>
+- Check if <a href="awstats_config.html#LogFormat">LogFormat</a> is
+set to "1" (for "NCSA apache combined/ELF/XLF log format")
+or use a custom log format if you don't use the combined log format.<br>
+- Set the <a href="awstats_config.html#SiteDomain">SiteDomain</a>
+parameter to the main domain name or the intranet web server name
+used to reach the web site to analyze (Example: www.mysite.com). If
+you have several
+possible names for same site, use the main domain name and add the
+others to the list in the <a href="awstats_config.html#HostAlias">HostAlias</a>
+parameter.<br>
+- You can also change other parameters if you want. The full list is
+described in <a href="awstats_config.html">Configurations/Directives
+options</a> page.<br>
+<br>
+Installation and configuration is finished. You can jump to the <a
+ href="#BUILD_UPDATE">Process logs: Building/updating statistics
+database</a> section.<br>
<br>
<br>
<br>
-<a name="INSTALLIIS"><b>B) Setup for Microsoft's IIS server</b></a><br>\r
-<br>
-<font style="color: rgb(17, 17, 85);"><b>* Step 1</b>:</font><br>\r
-<br>
-Configure IIS to log in the <b>"Extended W3C log format"</b> (You can\r
-still use\r
-your own custom log format but setup is easier if you use the standard\r
-extended format). To do so, start the IIS management console snap-in,\r
-select the\r
-appropriate web site and open its\r
-<span style="font-weight: bold;">Properties</span>. Choose "<span\r
- style="font-weight: bold;">W3C Extended Log Format</span>", then <span\r
- style="font-weight: bold;">Properties</span>, then the\r
-Tab "<span style="font-weight: bold;">Extended Properties</span>" and\r
-uncheck everything under Extended\r
-Properties.\r
-Once they are all cleared, check just the following fields:<br>\r
+<a name="INSTALLIIS"><b>B) Setup for Microsoft's IIS server</b></a><br>
+<br>
+<font style="color: rgb(17, 17, 85);"><b>* Step 1</b>:</font><br>
+<br>
+Configure IIS to create logs in the <b>"Extended W3C log format"</b> (You can
+still use
+your own custom log format but setup is easier if you use the standard
+extended format). To do so, start the IIS management console snap-in,
+select the
+appropriate web site and open its
+<span style="font-weight: bold;">Properties</span>. Choose "<span
+ style="font-weight: bold;">W3C Extended Log Format</span>", then <span
+ style="font-weight: bold;">Properties</span>, then the
+Tab "<span style="font-weight: bold;">Extended Properties</span>" and
+uncheck everything under Extended
+Properties.
+Once they are all cleared, check just the following fields:<br>
<table width="95%" border=1 cellpadding=0 cellspacing=0 bgcolor=#F4F4F4 class=CFAQ><tr class=CFAQ><td class=CFAQ>
-date<br>\r
-time<br>\r
-c-ip<br>\r
-cs-username<br>\r
-cs-method<br>\r
-cs-uri-stem<br>\r
-cs-uri-query<br>\r
-sc-status<br>\r
-sc-bytes<br>\r
-cs-version<br>\r
-cs(User-Agent)<br>\r
-cs(Referer)<br>\r
+date<br>
+time<br>
+c-ip<br>
+cs-username<br>
+cs-method<br>
+cs-uri-stem<br>
+cs-uri-query<br>
+sc-status<br>
+sc-bytes<br>
+cs-version<br>
+cs(User-Agent)<br>
+cs(Referer)<br>
</td></tr></table>
-<br>\r
-To be sure the log format change is effective, you must stop IIS,\r
-backup (if desired) and remove all old log files, restart IIS and go to\r
-your homepage. This is an example of the type of records you should\r
-find in the\r
-new log file:<br>\r
+<br>
+To be sure the log format change is effective, you must stop IIS,
+backup it up (if you desire) and remove all of the old log files, restart IIS and go to
+your homepage. This is an example of the type of records you should
+find in the
+new log file:<br>
<table width="95%" border=1 cellpadding=0 cellspacing=0 bgcolor=#F4F4F4 class=CFAQ><tr class=CFAQ><td class=CFAQ>
-2000-07-19 14:14:14 62.161.78.73 - GET / 200 1234 HTTP/1.1\r
-Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0)\r
-http://www.from.com/from.htm\r
+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
</td></tr></table>
<br>
-<font style="color: rgb(17, 17, 85);"><b>* Step 2</b>:</font><br>\r
-<br>
-Copy the contents of the AWStats provided cgi-bin folder from where\r
-your AWStats package put it on your local hard\r
-drive\r
-to your server's cgi-bin\r
-directory (this includes <b>awstats.pl</b>, <b>awstats.model.conf</b>,\r
-and the <b>lang</b>, <b>lib</b> and <b>plugins</b> sub-directories).<br>\r
-<br>\r
-<font style="color: rgb(17, 17, 85);"><b>* Step 3</b>:</font><br>\r
-<br>\r
-Move AWStats <b>icon sub-directories</b> and its content into a\r
-directory readable by your\r
-web server, for example C:\yourwwwroot\icon.<br>\r
-<br>\r
-<font style="color: rgb(17, 17, 85);"><b>* Step 4</b>:</font><br>\r
-<br>\r
-Create a configuration file by copying <b>awstats.model.conf</b> to a\r
-new file named <b>awstats.<span style="font-style: italic;">mysite</span>.conf</b>\r
-where "<span style="font-style: italic;">mysite</span>" is a\r
-value of your choice but usually is the domain or virtual host name.\r
-This new file must be saved in the same directory as awstats.pl (i.e.\r
-cgi-bin).<br>\r
-<br>\r
-<font style="color: rgb(17, 17, 85);"><b>* Step 5</b>:</font><br>\r
-<br>\r
-Edit your new <b>awstats.<span style="font-style: italic;">mysite</span>.conf</b>\r
-file to match your specific environment:<br>\r
-- Change the <a href="awstats_config.html#LogFile">LogFile</a> value\r
-to the\r
-full path of your web server log file (You\r
-can also use a relative path from your awstats.pl (cgi-bin) directory).<br>\r
-- Change the <a href="awstats_config.html#LogType">LogType</a> value\r
-to\r
-"W" for analyzing\r
-web log files.<br>\r
-- Change the <a href="awstats_config.html#LogFormat">LogFormat</a> to\r
-2 if you are using the <b>"Extended W3C log format"</b> described in\r
-step 1; in the case of a custom format, list the IIS fields\r
-being logged, for example:<br>\r
-<i>LogFormat="date time c-ip cs-username cs-method cs-uri-stem\r
-cs-uri-query sc-status sc-bytes cs-version cs(User-Agent) cs(Referer)"</i><br>\r
-- Change the <a href="awstats_config.html#DirIcons">DirIcons</a>\r
-parameter\r
-to reflect relative path of icon directory.<br>\r
-- Set the <a href="awstats_config.html#SiteDomain">SiteDomain</a>\r
-parameter to the main domain name or the intranet\r
-web server name used to reach the web site being analyzed (Example:\r
-www.mydomain.com).<br>\r
-- Set the <a href="awstats_config.html#AllowToUpdateStatsFromBrowser">AllowToUpdateStatsFromBrowser</a>\r
-parameter to 1 if you don't have command line access and have only cgi\r
-access.<br>\r
-- Review and change other parameters if appropriate.<br>\r
-<br>\r
-Installation and configuration is finished. You can jump to the <a\r
- href="#BUILD_UPDATE">Process logs: Building/Updating statistics\r
-database</a> section.<br>\r
-<br>\r
-<b>C) Setup for other web servers</b><br>\r
-<br>\r
-The setup process is similar to the setup for Apache or IIS.<br>\r
-Use <a href="awstats_config.html#LogFormat">LogFormat</a> to value "3"\r
-if you have WebStar native log format, use\r
-a personalized <a href="awstats_config.html#LogFormat">LogFormat</a>\r
-if your log format is other.<br>\r
-<br>\r
-<b>D) Setup for other Internet servers, i.e. FTP, Mail, Streaming media</b><br>\r
-<br>\r
-The setup process for other file formats is described in the relevant\r
-FAQ topics: \r
-<a href="awstats_faq.html#FTP">FAQ-COM090: FTP</a> \r
-<a href="awstats_faq.html#MAIL">FAQ-COM100: Mail</a> and <a\r
- href="awstats_faq.html#MEDIASERVER">FAQ-COM110: Streaming media</a>.<br>\r
-<br>\r
+<font style="color: rgb(17, 17, 85);"><b>* Step 2</b>:</font><br>
+<br>
+Copy the contents of the AWStats provided cgi-bin folder, from where
+the AWStats package put it on your local hard
+drive,
+to your server's cgi-bin
+directory (this includes <b>awstats.pl</b>, <b>awstats.model.conf</b>,
+and the <b>lang</b>, <b>lib</b> and <b>plugins</b> sub-directories).<br>
+<br>
+<font style="color: rgb(17, 17, 85);"><b>* Step 3</b>:</font><br>
+<br>
+Move AWStats <b>icon sub-directories</b> and its content into a
+directory readable by your
+web server, for example C:\yourwwwroot\icon.<br>
+<br>
+<font style="color: rgb(17, 17, 85);"><b>* Step 4</b>:</font><br>
+<br>
+Create a configuration file by copying <b>awstats.model.conf</b> to a
+new file named <b>awstats.<span style="font-style: italic;">mysite</span>.conf</b>
+where "<span style="font-style: italic;">mysite</span>" is a
+value of your choice but usually is the domain or virtual host name.
+This new file must be saved in the same directory as awstats.pl (i.e.
+cgi-bin).<br>
+<br>
+<font style="color: rgb(17, 17, 85);"><b>* Step 5</b>:</font><br>
+<br>
+Edit your new <b>awstats.<span style="font-style: italic;">mysite</span>.conf</b>
+file to match your specific environment:<br>
+- Change the <a href="awstats_config.html#LogFile">LogFile</a> value
+to the
+full path of your web server log file (You
+can also use a relative path from your awstats.pl (cgi-bin) directory).<br>
+- Change the <a href="awstats_config.html#LogType">LogType</a> value
+to
+"W" for analyzing
+web log files.<br>
+- Change the <a href="awstats_config.html#LogFormat">LogFormat</a> to
+2 if you are using the <b>"Extended W3C log format"</b> described in
+step 1; in the case of a custom format, list the IIS fields
+being logged, for example:<br>
+<i>LogFormat="date time c-ip cs-username cs-method cs-uri-stem
+cs-uri-query sc-status sc-bytes cs-version cs(User-Agent) cs(Referer)"</i><br>
+- Change the <a href="awstats_config.html#DirIcons">DirIcons</a>
+parameter
+to reflect relative path of icon directory.<br>
+- Set the <a href="awstats_config.html#SiteDomain">SiteDomain</a>
+parameter to the main domain name or the intranet
+web server name used to reach the web site being analyzed (Example:
+www.mydomain.com).<br>
+- Set the <a href="awstats_config.html#AllowToUpdateStatsFromBrowser">AllowToUpdateStatsFromBrowser</a>
+parameter to 1 if you don't have command line access and have only cgi
+access.<br>
+- Review and change other parameters if appropriate.<br>
+<br>
+Installation and configuration is finished. You can jump to the <a
+ href="#BUILD_UPDATE">Process logs: Building/Updating statistics
+database</a> section.<br>
+<br>
+<b>C) Setup for other web servers</b><br>
+<br>
+The setup process is similar to the setup for Apache or IIS.<br>
+Use <a href="awstats_config.html#LogFormat">LogFormat</a> to value "3"
+if you have WebStar native log format.
+Use a personalized <a href="awstats_config.html#LogFormat">LogFormat</a>
+if your log format is other.<br>
+<br>
+<b>D) Setup for other Internet servers, i.e. FTP, Mail, Streaming media</b><br>
+<br>
+The setup process for other file formats is described in the relevant
+FAQ topics:
+<a href="awstats_faq.html#FTP">FAQ-COM090: FTP</a>
+<a href="awstats_faq.html#MAIL">FAQ-COM100: Mail</a> and <a
+ href="awstats_faq.html#MEDIASERVER">FAQ-COM110: Streaming media</a>.<br>
+<br>
<br>
-<a name="BUILD_UPDATE">\r
-<h2 style=""><u>II. Process logs: Building/updating statistics database</u></h2>\r
-</a><br>\r
-<font style="color: rgb(17, 17, 85);"><b>* Update from command line (recommanded)</b>:</font><br>\r
-<br>\r
-The first log analysis should be done\r
-manually from the command line since the\r
-process may be long and it's easier to solve problems when you can see\r
-the\r
-command output (if you don't\r
-have Command Line access, skip to Step 2). The\r
-AWStats create (and update) statistics database command is:<br>\r
-<br>\r
+<a name="BUILD_UPDATE">
+<h2 style=""><u>II. Process logs: Building/updating statistics database</u></h2>
+</a><br>
+<font style="color: rgb(17, 17, 85);"><b>* Update from command line (recommanded)</b>:</font><br>
+<br>
+The first log analysis should be done
+manually from the command line since the
+process may be long and it's easier to solve problems when you can see
+the
+command output (if you don't
+have Command Line access, skip to Step 2). The
+AWStats create (and update) statistics database command is:<br>
+<br>
<table border=1 cellpadding=1 cellspacing=0 bgcolor=#F4F4F4 width="95%" class=CFAQ><tr class=CFAQ><td class=CFAQ>
perl awstats.pl -config=mysite -update
-</td></tr></table>\r
-<br>\r
-where <span style="font-style: italic;">mysite</span> must\r
-be substituted with the domain/virtual host name you selected earlier\r
-during AWStats configuration.<br>\r
-<br>\r
-AWStats will read the configuration file awstats.mysite.conf\r
-(or if\r
-not found, awstats.conf)\r
-and create/update its database with all summary information issued from\r
-analyzed log file.<br>\r
-<br>\r
-AWStats statistics database files are saved in directory defined by the\r
-<a href="awstats_config.html#DirData">DirData</a> parameter in\r
-configuration file.<br>\r
-When the create/update is finished, you should see a similar result on\r
-your screen:<br>\r
-<br>\r
+</td></tr></table>
+<br>
+where <span style="font-style: italic;">mysite</span> must
+be substituted with the domain/virtual host name you selected earlier
+during AWStats configuration.<br>
+<br>
+AWStats will read the configuration file awstats.mysite.conf
+(or if
+not found, awstats.conf)
+and create/update its database with all summary information issued from
+analyzed log file.<br>
+<br>
+AWStats statistics database files are saved in directory defined by the
+<a href="awstats_config.html#DirData">DirData</a> parameter in
+configuration file.<br>
+When the create/update is finished, you should see a similar result on
+your screen:<br>
+<br>
<table width="95%" border=1 cellpadding=0 cellspacing=0 bgcolor=#F4F4F4 class=CFAQ><tr class=CFAQ><td class=CFAQ>
-Update for config "/etc/awstats/awstats.mysite.conf"<br>\r
+Update for config "/etc/awstats/awstats.mysite.conf"<br>
With data in log file "/pathtoyourlog/yourlog.log"...<br>
Phase 1 : First bypass old records, searching new record...<br>
Searching new records from beginning of log file...<br>
-Phase 2 : Now process new records (Flush history on disk after 20000\r
-hosts)...<br>\r
+Phase 2 : Now process new records (Flush history on disk after 20000
+hosts)...<br>
Jumped lines in file: 0<br>
Parsed lines in file: 225730<br>
Found 122 dropped records,<br>
Found 87 corrupted records,<br>
Found 0 old records,<br>
- Found 225521 new qualified records.<br>\r
+ Found 225521 new qualified records.<br>
</td></tr></table>
<br>
-<b>Dropped records</b> are records discarded because they were not\r
-"user HTTP requests" or were requests matching AWStats filters (See the\r
-<a href="awstats_config.html#SkipHosts">SkipHosts</a>,\r
-<a href="awstats_config.html#SkipUserAgents">SkipUserAgents</a>,\r
-<a href="awstats_config.html#SkipFiles">SkipFiles</a>, <a\r
- href="awstats_config.html#OnlyHosts">OnlyHosts</a>,\r
-<a href="awstats_config.html#OnlyUserAgents">OnlyUserAgents</a> and <a\r
- 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>\r
-option on the command line.<br>\r
-<br>\r
-<b>Corrupted records</b> are records that does not match log format\r
-defined by "LogFormat" parameter in AWStats configuration file.\r
-All web servers will typically have a few corrupted records\r
-(<5%) even when everything works correctly.\r
-This can result for several reasons: 1) Web server internal bugs,\r
-2) bad requests made by buggy browsers, 3) a dirty web server shutdown,\r
-such as unplugging the server... <br>\r
-<br>\r
-If all your lines are corrupted and the <a\r
- href="awstats_config.html#LogFormat">LogFormat</a> parameter in\r
-AWStats configuration file is\r
-correct, there may be a setup problem with your web server log format.\r
-Don't forget that\r
-your <a href="awstats_config.html#OnlyFiles">LogFormat</a> parameter\r
-in the AWStats configuration file MUST match\r
-the log file format you analyze. If you want to see which lines\r
-are corrupted, you can add the <b>-showcorrupted</b>\r
-option on the command line.<br>\r
-<br>\r
-<b>Old records</b> are simply records that were already processed by a\r
-previous update session.\r
-Although it is not necessary to purge your log file after\r
-each update process, it is highly recommended that you do so as often\r
-as possible.<br>\r
-<br>\r
-<b>New records</b> are records in your log file that were successfully\r
-used to build/update the statistics database.<br>\r
-<br>\r
-Note: A log analysis process might be slow (one second for each 4500\r
-lines of your\r
-logfile with an Athlon 1Ghz, plus DNS resolution time for each\r
-different\r
-IP\r
-address in your logfile if <a href="awstats_config.html#DNSLookup">DNSLookup</a>\r
-is set to 1 and not already done in your log file). See the <a\r
- href="awstats_benchmark.html">Benchmarks page</a> for more detailed\r
-information.<br>\r
-<br>\r
-<!-- <span style="font-weight: bold;">Flush history </span>messages referer\r
-to ... (Flush history on disk after 20000 hosts). Flush history\r
-file on disk (unique url reach flush limit of 5000 -->\r
-\r
-<br>\r
-<font style="color: rgb(17, 17, 85);"><b>* Update from a browser</b>:</font><br>\r
-<br>\r
-AWStats statistics can also be updated from a browser, providing\r
-real-time statistics, by clicking\r
-the "Update now" link that appears when AWStats is used as a CGI (The\r
-URL is described in the next\r
-section '<a href="#READ">Run reports: Building and reading reports</a>').<br>\r
+<b>Dropped records</b> are records discarded because they were not
+"user HTTP requests" or were requests matching AWStats filters (See the
+<a href="awstats_config.html#SkipHosts">SkipHosts</a>,
+<a href="awstats_config.html#SkipUserAgents">SkipUserAgents</a>,
+<a href="awstats_config.html#SkipFiles">SkipFiles</a>, <a
+ href="awstats_config.html#OnlyHosts">OnlyHosts</a>,
+<a href="awstats_config.html#OnlyUserAgents">OnlyUserAgents</a> and <a
+ href="awstats_config.html#OnlyFiles">OnlyFiles</a> parameters).
+If you want to see which lines were dropped, you can add the <b>-showdropped</b>
+option on the command line.<br>
+<br>
+<b>Corrupted records</b> are records that do not match the log format
+defined by the "LogFormat" parameter in the AWStats configuration file.
+All web servers will typically have a few corrupted records
+(<5%) even when everything works correctly.
+This can result for several reasons: 1) Web server internal bugs,
+2) bad requests made by buggy browsers, 3) a dirty web server shutdown,
+such as unplugging the server... <br>
+<br>
+If all of your lines are corrupted and the <a
+ href="awstats_config.html#LogFormat">LogFormat</a> parameter in
+AWStats configuration file is
+correct, then there may be a setup problem with your web server log format.
+Don't forget that
+your <a href="awstats_config.html#OnlyFiles">LogFormat</a> parameter
+in the AWStats configuration file MUST match
+the log file format you analyze. If you want to see which lines
+are corrupted, you can add the <b>-showcorrupted</b>
+option on the command line.<br>
+<br>
+<b>Old records</b> are simply records that were already processed by a
+previous update session.
+Although it is not necessary to purge your log file after
+each update process, it is highly recommended that you do so as often
+as possible.<br>
+<br>
+<b>New records</b> are records in your log file that were successfully
+used to build/update the statistics database.<br>
+<br>
+Note: A log analysis process might be slow (one second for each 4500
+lines of your
+logfile with an Athlon 1Ghz, plus DNS resolution time for each
+different
+IP
+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). See the <a
+ href="awstats_benchmark.html">Benchmarks page</a> for more detailed
+information.<br>
+<br>
+<!-- <span style="font-weight: bold;">Flush history </span>messages referer
+to ... (Flush history on disk after 20000 hosts). Flush history
+file on disk (unique url reach flush limit of 5000 -->
+
+<br>
+<font style="color: rgb(17, 17, 85);"><b>* Update from a browser</b>:</font><br>
+<br>
+AWStats statistics can also be updated from a browser, providing
+real-time statistics, by clicking
+the "Update now" link that appears when AWStats is used as a CGI (The
+URL is described in the next
+section '<a href="#READ">Run reports: Building and reading reports</a>').<br>
<br>
<b>Warning</b>!!<br>
-To enable this link, the configuration file parameter <a\r
- href="awstats_config.html#AllowToUpdateStatsFromBrowser">AllowToUpdateStatsFromBrowser</a>\r
-must be set to 1 (The link is not enabled by\r
-default).<br>\r
-Using the on-line update does not prevent you from running the update\r
-process automatically on a scheduled basis (the command is same as that\r
-of the first update process above).<br>\r
+To enable this link, the configuration file parameter <a
+ href="awstats_config.html#AllowToUpdateStatsFromBrowser">AllowToUpdateStatsFromBrowser</a>
+must be set to 1 (The link is not enabled by
+default).<br>
+Using the on-line update does not prevent you from running the update
+process automatically on a scheduled basis (the command is same as that
+of the first update process above).<br>
For this, you have two choices:<br>
-- Include the update command in your <b>logrotate</b> process. See <a\r
- href="awstats_faq.html#ROTATE">FAQ-COM120</a> for details.<br>\r
-- Or add instructions in your <b>crontab</b> (Unix/Linux) or your <b>task\r
-scheduler</b> (Windows), to regularly launch the Awstats update\r
-process. See <a href="awstats_faq.html#CRONTAB">FAQ-COM130</a> for\r
-details.<br>\r
-<br>\r
-See the AWStats <a href="awstats_benchmark.html">Benchmarks page</a>\r
-for\r
-the recommended update/logrotate frequency.<br>\r
+- Include the update command in your <b>logrotate</b> process. See <a
+ href="awstats_faq.html#ROTATE">FAQ-COM120</a> for details.<br>
+- Or add instructions in your <b>crontab</b> (Unix/Linux) or your <b>task
+scheduler</b> (Windows), to regularly launch the Awstats update
+process. See <a href="awstats_faq.html#CRONTAB">FAQ-COM130</a> for
+details.<br>
+<br>
+See the AWStats <a href="awstats_benchmark.html">Benchmarks page</a>
+for
+the recommended update/logrotate frequency.<br>
<br>
<br>
-<a name="READ">\r
-<h2 style=""><u>III. Run reports: Building and reading reports</u></h2>\r
-</a><br>\r
-To see the analysis results, you have several options depending on your\r
-<a href="awstats_security.html">security policy</a>.<br>\r
-<br>\r
-Note: you must have created a statistics data base for the analysis\r
-period by processing your\r
-log files before you try to create reports. See the previous\r
-section.<br>\r
-<br>\r
-1. The first option is to build the main reports, in a static HTML\r
-page,\r
-from the command line,\r
-using the following syntax (skip to the second option if you only have\r
-CGI access):<br>\r
-<br>\r
+<a name="READ">
+<h2 style=""><u>III. Run reports: Building and reading reports</u></h2>
+</a><br>
+To see the analysis results, you have several options depending on your
+<a href="awstats_security.html">security policy</a>.<br>
+<br>
+Note: you must have created a statistics data base for the analysis
+period by processing your
+log files before you try to create reports. See the previous
+section.<br>
+<br>
+1. The first option is to build the main reports, in a static HTML
+page,
+from the command line,
+using the following syntax (skip to the second option if you only have
+CGI access):<br>
+<br>
<table border=1 cellpadding=1 cellspacing=0 bgcolor=#F4F4F4 width="95%" class=CFAQ><tr class=CFAQ><td class=CFAQ>
-perl awstats.pl -config=mysite -output -staticlinks\r
-> awstats.mysite.html\r
+perl awstats.pl -config=mysite -output -staticlinks
+> awstats.mysite.html
</td></tr></table>
-<br>\r
-where <span style="font-style: italic;">mysite</span> must\r
-be substituted with the domain/virtual host name you selected earlier\r
-during AWStats configuration.<br>\r
-<br>
-To create specific individual reports, specify the report name on the\r
-command\r
-line as follows¹:<br>\r
+<br>
+where <span style="font-style: italic;">mysite</span> must
+be substituted with the domain/virtual host name you selected earlier
+during AWStats configuration.<br>
+<br>
+To create specific individual reports, specify the report name on the
+command
+line as follows¹:<br>
<table border=1 cellpadding=1 cellspacing=0 bgcolor=#F4F4F4 width="95%" class=CFAQ><tr class=CFAQ><td class=CFAQ>
-perl awstats.pl -config=mysite -output=alldomains\r
--staticlinks > awstats.mysite.alldomains.html<br>\r
-perl awstats.pl -config=mysite -output=allhosts\r
--staticlinks > awstats.mysite.allhosts.html<br>\r
-perl awstats.pl -config=mysite -output=lasthosts\r
--staticlinks > awstats.mysite.lasthosts.html<br>\r
-perl awstats.pl -config=mysite -output=unknownip\r
--staticlinks > awstats.mysite.unknownip.html<br>\r
-perl awstats.pl -config=mysite -output=alllogins\r
--staticlinks > awstats.mysite.alllogins.html<br>\r
-perl awstats.pl -config=mysite -output=lastlogins\r
--staticlinks > awstats.mysite.lastlogins.html<br>\r
-perl awstats.pl -config=mysite -output=allrobots\r
--staticlinks > awstats.mysite.allrobots.html<br>\r
-perl awstats.pl -config=mysite -output=lastrobots\r
--staticlinks > awstats.mysite.lastrobots.html<br>\r
-perl awstats.pl -config=mysite -output=urldetail\r
--staticlinks > awstats.mysite.urldetail.html<br>\r
-perl awstats.pl -config=mysite -output=urlentry\r
--staticlinks > awstats.mysite.urlentry.html<br>\r
-perl awstats.pl -config=mysite -output=urlexit\r
--staticlinks > awstats.mysite.urlexit.html<br>\r
-perl awstats.pl -config=mysite -output=browserdetail\r
--staticlinks > awstats.mysite.browserdetail.html<br>\r
-perl awstats.pl -config=mysite -output=osdetail\r
--staticlinks > awstats.mysite.osdetail.html<br>\r
-perl awstats.pl -config=mysite -output=unknownbrowser\r
--staticlinks > awstats.mysite.unknownbrowser.html<br>\r
-perl awstats.pl -config=mysite -output=unknownos\r
--staticlinks > awstats.mysite.unknownos.html<br>\r
-perl awstats.pl -config=mysite -output=refererse\r
--staticlinks > awstats.mysite.refererse.html<br>\r
-perl awstats.pl -config=mysite -output=refererpages\r
--staticlinks > awstats.mysite.refererpages.html<br>\r
-perl awstats.pl -config=mysite -output=keyphrases\r
--staticlinks > awstats.mysite.keyphrases.html<br>\r
-perl awstats.pl -config=mysite -output=keywords\r
--staticlinks > awstats.mysite.keywords.html<br>\r
-perl awstats.pl -config=mysite -output=errors404\r
--staticlinks > awstats.mysite.errors404.html<br>\r
+perl awstats.pl -config=mysite -output=alldomains
+-staticlinks > awstats.mysite.alldomains.html<br>
+perl awstats.pl -config=mysite -output=allhosts
+-staticlinks > awstats.mysite.allhosts.html<br>
+perl awstats.pl -config=mysite -output=lasthosts
+-staticlinks > awstats.mysite.lasthosts.html<br>
+perl awstats.pl -config=mysite -output=unknownip
+-staticlinks > awstats.mysite.unknownip.html<br>
+perl awstats.pl -config=mysite -output=alllogins
+-staticlinks > awstats.mysite.alllogins.html<br>
+perl awstats.pl -config=mysite -output=lastlogins
+-staticlinks > awstats.mysite.lastlogins.html<br>
+perl awstats.pl -config=mysite -output=allrobots
+-staticlinks > awstats.mysite.allrobots.html<br>
+perl awstats.pl -config=mysite -output=lastrobots
+-staticlinks > awstats.mysite.lastrobots.html<br>
+perl awstats.pl -config=mysite -output=urldetail
+-staticlinks > awstats.mysite.urldetail.html<br>
+perl awstats.pl -config=mysite -output=urlentry
+-staticlinks > awstats.mysite.urlentry.html<br>
+perl awstats.pl -config=mysite -output=urlexit
+-staticlinks > awstats.mysite.urlexit.html<br>
+perl awstats.pl -config=mysite -output=browserdetail
+-staticlinks > awstats.mysite.browserdetail.html<br>
+perl awstats.pl -config=mysite -output=osdetail
+-staticlinks > awstats.mysite.osdetail.html<br>
+perl awstats.pl -config=mysite -output=unknownbrowser
+-staticlinks > awstats.mysite.unknownbrowser.html<br>
+perl awstats.pl -config=mysite -output=unknownos
+-staticlinks > awstats.mysite.unknownos.html<br>
+perl awstats.pl -config=mysite -output=refererse
+-staticlinks > awstats.mysite.refererse.html<br>
+perl awstats.pl -config=mysite -output=refererpages
+-staticlinks > awstats.mysite.refererpages.html<br>
+perl awstats.pl -config=mysite -output=keyphrases
+-staticlinks > awstats.mysite.keyphrases.html<br>
+perl awstats.pl -config=mysite -output=keywords
+-staticlinks > awstats.mysite.keywords.html<br>
+perl awstats.pl -config=mysite -output=errors404
+-staticlinks > awstats.mysite.errors404.html<br>
</td></tr></table>
-<br>\r
-¹If you prefer, you can use the <a\r
- href="awstats_tools.html#awstats_buildstaticpages">awstats_buildstaticpages</a>\r
-tool to\r
-build all these pages in one command, or to generate PDF files.<br>\r
-<br>\r
-Notes:<br>\r
-<br>\r
-a) You can also add a <i>filter</i> on the following reports: <b>urldetail,\r
-urlentry, urlexit, allhosts, refererpages</b>. The <i>filter</i>\r
-can be a regexp (regular expression) on the full key you want AWStats\r
-to report on and is appended to the output\r
+<br>
+¹If you prefer, you can use the <a
+ href="awstats_tools.html#awstats_buildstaticpages">awstats_buildstaticpages</a>
+tool to
+build all these pages in one command, or to generate PDF files.<br>
+<br>
+Notes:<br>
+<br>
+a) You can also add a <i>filter</i> on the following reports: <b>urldetail,
+urlentry, urlexit, allhosts, refererpages</b>. The <i>filter</i>
+can be a regexp (regular expression) on the full key you want AWStats
+to report on and is appended to the output
parameter separated by a ":".<br>
-<br>\r
-For example, to output the urldetail report, including only pages which\r
-contain /news in their URL, you\r
+<br>
+For example, to output the urldetail report, including only pages which
+contain /news in their URL, you
can use the following command line:<br>
<table border=1 cellpadding=1 cellspacing=0 bgcolor=#F4F4F4 width="95%" class=CFAQ><tr class=CFAQ><td class=CFAQ>
-perl awstats.pl -config=mysite -output=urldetail:</b>/news<b>\r
--staticlinks > awstats.mysite.urldetailwithfilter.html</b>\r
+perl awstats.pl -config=mysite -output=urldetail:</b>/news<b>
+-staticlinks > awstats.mysite.urldetailwithfilter.html</b>
</td></tr></table>
-<br>\r
-b) If you want to build a report for a particular month, add\r
-the options <i><b>-month=MM -year=YYYY</b></i> where MM is the month\r
-expressed as two digits, i.e. 03, and year is the four digit\r
-year. To build a\r
-report for a full year, add the options <i><b>-month=all -year=YYYY</b></i>\r
-(warning: this is often resource intensive and might use a lot of\r
-memory\r
-and CPU. Unix/Linux like operating systems might benefit from use\r
-of the "nice" command.)<br>\r
-<br>\r
-<br>\r
-2) The second option is to dynamically view your statistics from a\r
-browser. To do this, use the URL:<br>\r
+<br>
+b) If you want to build a report for a particular month, add
+the options <i><b>-month=MM -year=YYYY</b></i> where MM is the month
+expressed as two digits, i.e. 03, and year is the four digit
+year. To build a
+report for a full year, add the options <i><b>-month=all -year=YYYY</b></i>
+(warning: this is often resource intensive and might use a lot of
+memory
+and CPU. Unix/Linux like operating systems might benefit from use
+of the "nice" command.)<br>
+<br>
+<br>
+2) The second option is to dynamically view your statistics from a
+browser. To do this, use the URL:<br>
<table border=1 cellpadding=1 cellspacing=0 bgcolor=#F4F4F4 width="95%" class=CFAQ><tr class=CFAQ><td class=CFAQ>
-http://www.myserver.mydomain/awstats/awstats.pl?config=mysite\r
+http://www.myserver.mydomain/awstats/awstats.pl?config=mysite
</td></tr></table>
-<br>\r
-where <i>mysite</i> specifies the configuration\r
-file to\r
-use (AWStats will use the file awstats.<i>mysite</i>.conf).<br>\r
-<br>\r
-All output command line options (except -staticlinks) are\r
-also available when using AWStats with a browser. Just use them as URL\r
-parameters: change "-option" to\r
-"&option", i.e. <b><i>http://www.myserver.mydomain/awstats/awstats.pl?month=MM&year=YYYY&output=unknownos</i></b><br>\r
-<br>\r
-Reports are generated in real time from the statistics data\r
-base. If this is slow, or putting too much load on your server,\r
-consider generating static reports instead.<br>\r
-<br>\r
-If the <a href="awstats_config.html#AllowToUpdateStatsFromBrowser">AllowToUpdateStatsFromBrowser</a>\r
-parameter is set to 1 in AWStats configuration file,\r
-you will also be able to run the update process from your browser. Just\r
-click on the link "Update now".<br>\r
-<br>\r
+<br>
+where <i>mysite</i> specifies the configuration
+file to
+use (AWStats will use the file awstats.<i>mysite</i>.conf).<br>
+<br>
+All output command line options (except -staticlinks) are
+also available when using AWStats with a browser. Just use them as URL
+parameters: change "-option" to
+"&option", i.e. <b><i>http://www.myserver.mydomain/awstats/awstats.pl?month=MM&year=YYYY&output=unknownos</i></b><br>
+<br>
+Reports are generated in real time from the statistics data
+base. If this is slow, or putting too much load on your server,
+consider generating static reports instead.<br>
+<br>
+If the <a href="awstats_config.html#AllowToUpdateStatsFromBrowser">AllowToUpdateStatsFromBrowser</a>
+parameter is set to 1 in AWStats configuration file,
+you will also be able to run the update process from your browser. Just
+click on the link "Update now".<br>
+<br>
<br>
<hr>
-<script language="javascript">\r
+<script language="javascript">
var date='$Date$';
document.writeln("Last revision: "+date);
</script>
projects / thirdparty / AWStats.git / commitdiff
