From: eldy <> Date: Sat, 15 Nov 2003 17:13:02 +0000 (+0000) Subject: Updated documentation. X-Git-Tag: AWSTATS_6_0_BETA~118 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=78f9d6543b034a27e4c78aba2f2189c3c94335e5;p=thirdparty%2FAWStats.git Updated documentation. --- diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html index 36e8e34a..1bb6c870 100644 --- a/docs/awstats_faq.html +++ b/docs/awstats_faq.html @@ -521,7 +521,7 @@ process.
  • If your config file is setup with a LogFile parameter that point to your current running log file (required if you want to use the AllowToUpdateStatsFromBrowser -option to have "real-time" statistics), if you don't want to loose any records during the rotate +option to have "real-time" statistics), to avoid loosing too much records during the rotate process, you must run the AWStats update JUST BEFORE the rotate process is done.
    The best way to do that on Linux like OS is to use the linux built-in logrotate feature. You must edit the logrotate config file used for you web server log file (usually stored in /etc/logrotate.d @@ -544,9 +544,20 @@ postrotate
    endscript
    }
    -
    - -
  • If you choose to run the AWStats update process on the last archived log files, why not.
    +The advantage of this solution is that it is easy to setup and the data loss should not be +significant. You will still forget some of hits that occured after the end of the +awstats reading log and the apache change of its log target. This times depends on +time of writing updated awstats database but also time for apache threads to finish and this +is not same for all apache threads (threads busy or not). So as a conclusion, you will +loose some hits, but loss should not be significant in most cases. +What's really wrong is that the HUP signal kill the Apache thread if, after waiting +few milliseconds, it's still busy. This means that a transaction process might be killed +and visitor session disconnected.
    +Note also that if you have x logrotate config files with each of them a postrotate with a +kill -HUP, you send a kill x times your server process.
    +
    + +
  • You can also choose to run the AWStats update process on the last archived log files.
    This is required for example if you use the cronolog or rotatelog tools to rotate your log files. For example, Apache users can setup their Apache httpd config file to write log file through a pipe to cronolog or rotatelog using @@ -556,6 +567,19 @@ If you use a such feature, you can't trigger AWStats update process to be ran ju rotate is done, so you must run it AFTER the rotate process, so on the archived log file.
    To setup awstats to always point to last archive log file, you can use the 'tags' available for LogFile.
    +The problem with that is that your data are refreshed only after a rotate has done.
    +
    +
  • So, if you really want to not loose absolutely no hit and want to have updates more +frequently than the rotate frequency, the best way is still an hybrid solution (i am not sure +that it worth the pain, and remember that statistics are only statistics):
    +You run the awstats update process from you crontab every hour for example and half and hour +before the rotate has done. +Then, once the rotate has been done, and before the next scheduled awstats update process start, +you run another update process on the archived log file using the -logfile option to force +update on the archived log file and not the log file that is currently defined in awstats +config file and used by cron update. This will allow you to update the half hour missing, +until the log rotate (AWStats will find the new lines). However don't forget that this +particular update must finished before the next croned update.