field of output file. This can be used to add a cluster id<br>
when log files come from several load balanced computers.<br> -stoponfirsteof Stop processing when any logfile reaches end-of-file.<br> -printfields For IIS or W3C logs, prints the latest field header for<br>
the currentlog file when switching between log file entries<br>
-so that the parsercan automatically determine which fields<br> are avaiable.<br> -ignoremissing will not fail if a log file is missing<br><br>This runs logresolvemerge in command line to open one or several<br>server log files to merge them (sorted on date) and/or to make a reverse<br>DNS lookup (if asked). The result log file is sent on standard output.<br>Note: logresolvemerge is not a 'sort' tool to sort one file. It's a<br>software able to output sorted log records (with a reverse DNS lookup<br>included or not) even if log records are dispatched in several files.<br>Each of thoose files must be already independently sorted itself<br>(but that is the case in all web server log files). So you can use it<br>for load balanced log files or to group several old log files.<br><br>Don't forget that the main goal of logresolvemerge is to send log records to<br>a log analyzer in a sorted order without merging files on disk (NO NEED<br>OF DISK SPACE AT ALL) and without loading files into memory (NO NEED<br>OF MORE MEMORY). Choose of output records is done on the fly.<br><br>So logresolvemerge is particularly usefull when you want to output several<br>and/or large log files in a fast process, with no use of disk or<br>more memory, and in a chronological order through a pipe (to be used by a log<br>analyzer).<br><br>Note: If input records are not 'exactly' sorted but 'nearly' sorted (this<br>occurs with heavy servers), this is not a problem, the output will also<br>be 'nearly' sorted but a few log analyzers (like AWStats) knowns how to deal<br>with such logs.<br><br>WARNING: If log files are old MAC text files (lines ended with CR char), you<br>can't run this tool on Win or Unix platforms.<br><br>WARNING: Because of memory holes in ActiveState Perl version, use another<br>Perl interpreter if you need to process large log files.<br><br>Now supports/detects:<br> Automatic detection of log format<br> Files can be .gz/.bz2 files if zcat/bzcat tools are available in PATH.<br> Multithreaded reverse DNS lookup (several parallel requests) with Perl 5.8+.<br>New versions and FAQ at http://awstats.sourceforge.net<br>
+so that the parsercan automatically determine which fields<br> are avaiable.<br> -ignoremissing will not fail if a log file is missing<br><br>This runs logresolvemerge in command line to open one or several<br>server log files to merge them (sorted on date) and/or to make a reverse<br>DNS lookup (if asked). The result log file is sent on standard output.<br>Note: logresolvemerge is not a 'sort' tool to sort one file. It's a<br>software able to output sorted log records (with a reverse DNS lookup<br>included or not) even if log records are dispatched in several files.<br>Each of thoose files must be already independently sorted itself<br>(but that is the case in all web server log files). So you can use it<br>for load balanced log files or to group several old log files.<br><br>Don't forget that the main goal of logresolvemerge is to send log records to<br>a log analyzer in a sorted order without merging files on disk (NO NEED<br>OF DISK SPACE AT ALL) and without loading files into memory (NO NEED<br>OF MORE MEMORY). Choose of output records is done on the fly.<br><br>So logresolvemerge is particularly usefull when you want to output several<br>and/or large log files in a fast process, with no use of disk or<br>more memory, and in a chronological order through a pipe (to be used by a log<br>analyzer).<br><br>Note: If input records are not 'exactly' sorted but 'nearly' sorted (this<br>occurs with heavy servers), this is not a problem, the output will also<br>be 'nearly' sorted but a few log analyzers (like AWStats) knowns how to deal<br>with such logs.<br><br>WARNING: If log files are old MAC text files (lines ended with CR char), you<br>can't run this tool on Win or Unix platforms.<br><br>WARNING: Because of memory holes in ActiveState Perl version, use another<br>Perl interpreter if you need to process large log files.<br><br>Now supports/detects:<br> Automatic detection of log format<br> Files can be .gz/.bz2 files if zcat/bzcat tools are available in PATH.<br> Multithreaded reverse DNS lookup (several parallel requests) with Perl 5.8+.<br>New versions and FAQ at http://www.awstats.org<br>
<br>
<br>
<br>
<br>Example: urlaliasbuilder.pl -site=www.someotherhost.com
<br>
-<br>New versions and FAQ at http://awstats.sourceforge.net
+<br>New versions and FAQ at http://www.awstats.org
<br>
<br>This script was written from Simon Waight original works title-grabber.pl.
<br>
!define MUI_PROD "AWStats" ;Define your own software name here
#!define MUI_VERSION_DOT "7.0" ;Define your own software version here
!define MUI_PUBLISHER "Laurent Destailleur"
-!define MUI_URL "http://awstats.sourceforge.net"
+!define MUI_URL "http://www.awstats.org"
!define MUI_COMMENTS "copyright 2000/2010 Laurent Destailleur"
-!define MUI_HELPLINK "http://awstats.sourceforge.net/docs/index.html"
-!define MUI_URLUPDATE "http://awstats.sourceforge.net"
+!define MUI_HELPLINK "http://www.awstats.org/docs/index.html"
+!define MUI_URLUPDATE "http://www.awstats.org"
-<xml xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://awstats.sourceforge.net/files/awstats.xsd">
+<xml xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.awstats.org/files/awstats.xsd">
<version><lib>
AWSTATS DATA FILE 6.7 (build 1.892)
projects / thirdparty / AWStats.git / commitdiff
