Fórum Ubuntu CZ/SK

Ostatní => Archiv => Téma založeno: SupuS 02 Července 2006, 21:50:01

Název: webalizer na ubuntu dapper serveru - problem s cestinou
Přispěvatel: SupuS 02 Července 2006, 21:50:01
Ve statistikach webalizeru se mi nezobrazuji korektne ceske znaky .. nastavil jsem v konfiguracnim souboru webalizeru charset encoding na utf-8 i na iso-8859-2 a porad nic. Vypada to, ze jsou spatne znaky generovany primo webalizerem .. mozna tento problem souvisi s mym problemem s kodovanim v konzoli - http://forum.ubuntu.cz/viewtopic.php?pid=14891#p14891 ale nevim a proto jsem zalozil novy thread ..

info:

# locale
LANG=cs_CZ.UTF-8
LANGUAGE=cs_CZ:cs:en_GB:en
LC_CTYPE="cs_CZ.UTF-8"
LC_NUMERIC="cs_CZ.UTF-8"
LC_TIME="cs_CZ.UTF-8"
LC_COLLATE="cs_CZ.UTF-8"
LC_MONETARY="cs_CZ.UTF-8"
LC_MESSAGES="cs_CZ.UTF-8"
LC_PAPER="cs_CZ.UTF-8"
LC_NAME="cs_CZ.UTF-8"
LC_ADDRESS="cs_CZ.UTF-8"
LC_TELEPHONE="cs_CZ.UTF-8"
LC_MEASUREMENT="cs_CZ.UTF-8"
LC_IDENTIFICATION="cs_CZ.UTF-8"
LC_ALL=

# cat /etc/webalizer.conf

#
# Sample Webalizer configuration file
# Copyright 1997-2000 by Bradford L. Barrett (brad@mrunix.net)
#
# Distributed under the GNU General Public License.  See the
# files "Copyright" and "COPYING" provided with the webalizer
# distribution for additional information.
#
# This is a sample configuration file for the Webalizer (ver 2.01)
# Lines starting with pound signs '#' are comment lines and are
# ignored.  Blank lines are skipped as well.  Other lines are considered
# as configuration lines, and have the form "ConfigOption  Value" where
# ConfigOption is a valid configuration keyword, and Value is the value
# to assign that configuration option.  Invalid keyword/values are
# ignored, with appropriate warnings being displayed.  There must be
# at least one space or tab between the keyword and its value.
#
# As of version 0.98, The Webalizer will look for a 'default' configuration
# file named "webalizer.conf" in the current directory, and if not found
# there, will look for "/etc/webalizer.conf".


# LogFile defines the web server log file to use.  If not specified
# here or on on the command line, input will default to STDIN.  If
# the log filename ends in '.gz' (ie: a gzip compressed file), it will
# be decompressed on the fly as it is being read.

#LogFile        /var/lib/httpd/logs/access_log

# LogType defines the log type being processed.  Normally, the Webalizer
# expects a CLF or Combined web server log as input.  Using this option,
# you can process ftp logs as well (xferlog as produced by wu-ftp and
# others), or Squid native logs.  Values can be 'clf', 'ftp' or 'squid',
# with 'clf' the default.

#LogType        clf

# OutputDir is where you want to put the output files.  This should
# should be a full path name, however relative ones might work as well.
# If no output directory is specified, the current directory will be used.

#OutputDir      /var/lib/httpd/htdocs/usage

# HistoryName allows you to specify the name of the history file produced
# by the Webalizer.  The history file keeps the data for up to 12 months
# worth of logs, used for generating the main HTML page (index.html).
# The default is a file named "webalizer.hist", stored in the specified
# output directory.  If you specify just the filename (without a path),
# it will be kept in the specified output directory.  Otherwise, the path
# is relative to the output directory, unless absolute (leading /).

HistoryName        webalizer.hist

# Incremental processing allows multiple partial log files to be used
# instead of one huge one.  Useful for large sites that have to rotate
# their log files more than once a month.  The Webalizer will save its
# internal state before exiting, and restore it the next time run, in
# order to continue processing where it left off.  This mode also causes
# The Webalizer to scan for and ignore duplicate records (records already
# processed by a previous run).  See the README file for additional
# information.  The value may be 'yes' or 'no', with a default of 'no'.
# The file 'webalizer.current' is used to store the current state data,
# and is located in the output directory of the program (unless changed
# with the IncrementalName option below).  Please read at least the section
# on Incremental processing in the README file before you enable this option.

Incremental       yes

# IncrementalName allows you to specify the filename for saving the
# incremental data in.  It is similar to the HistoryName option where the
# name is relative to the specified output directory, unless an absolute
# filename is specified.  The default is a file named "webalizer.current"
# kept in the normal output directory.  If you don't specify "Incremental"
# as 'yes' then this option has no meaning.

IncrementalName        webalizer.current

# ReportTitle is the text to display as the title.  The hostname
# (unless blank) is appended to the end of this string (seperated with
# a space) to generate the final full title string.
# Default is (for english) "Usage Statistics for".

#ReportTitle    Usage Statistics for

# HostName defines the hostname for the report.  This is used in
# the title, and is prepended to the URL table items.  This allows
# clicking on URL's in the report to go to the proper location in
# the event you are running the report on a 'virtual' web server,
# or for a server different than the one the report resides on.
# If not specified here, or on the command line, webalizer will
# try to get the hostname via a uname system call.  If that fails,
# it will default to "localhost".

#HostName       localhost

# HTMLExtension allows you to specify the filename extension to use
# for generated HTML pages.  Normally, this defaults to "html", but
# can be changed for sites who need it (like for PHP embeded pages).

#HTMLExtension  html

# PageType lets you tell the Webalizer what types of URL's you
# consider a 'page'.  Most people consider html and cgi documents
# as pages, while not images and audio files.  If no types are
# specified, defaults will be used ('htm*', 'cgi' and HTMLExtension
# if different for web logs, 'txt' for ftp logs).

PageType        htm*
PageType        cgi
PageType        phtml
PageType        php*
PageType        jsp
PageType        shtm*
PageType        pl
PageType        jhtm*
PageType        asp
PageType        wml

# UseHTTPS should be used if the analysis is being run on a
# secure server, and links to urls should use 'https://' instead
# of the default 'http://'.  If you need this, set it to 'yes'.
# Default is 'no'.  This only changes the behaviour of the 'Top
# URL's' table.

#UseHTTPS       no

# DNSCache specifies the DNS cache filename to use for reverse DNS lookups.
# This file must be specified if you wish to perform name lookups on any IP
# addresses found in the log file.  If an absolute path is not given as
# part of the filename (ie: starts with a leading '/'), then the name is
# relative to the default output directory.  See the DNS.README file for
# additional information.

DNSCache        dns_cache.db

# DNSChildren allows you to specify how many "children" processes are
# run to perform DNS lookups to create or update the DNS cache file.
# If a number is specified, the DNS cache file will be created/updated
# each time the Webalizer is run, immediately prior to normal processing,
# by running the specified number of "children" processes to perform
# DNS lookups.  If used, the DNS cache filename MUST be specified as
# well.  The default value is zero (0), which disables DNS cache file
# creation/updates at run time.  The number of children processes to
# run may be anywhere from 1 to 100, however a large number may effect
# normal system operations.  Reasonable values should be between 5 and
# 20.  See the DNS.README file for additional information.

DNSChildren       5

# HTMLPre defines HTML code to insert at the very beginning of the
# file.  Default is the DOCTYPE line shown below.  Max line length
# is 80 characters, so use multiple HTMLPre lines if you need more.

HTMLPre

# HTMLHead defines HTML code to insert within the
# block, immediately after the line.  Maximum line length<br /># is 80 characters, so use multiple lines if needed.<br /><br />#HTMLHead <DEFANGED_META NAME="author" CONTENT="The Webalizer"><br />HTMLHead <meta http-equiv="Content-Type" content="text/html" charset="utf-8"><br /><br /># HTMLBody defined the HTML code to be inserted, starting with the<br /># <BODY> tag.  If not specified, the default is shown below.  If<br /># used, you MUST include your own <BODY> tag as the first line.<br /># Maximum line length is 80 char, use multiple lines if needed.<br /><br />#HTMLBody <BODY BGCOLOR="#E8E8E8" TEXT="#000000" LINK="#0000FF" VLINK="#FF0000"><br /><br /># HTMLPost defines the HTML code to insert immediately before the<br /># first <HR> on the document, which is just after the title and<br /># "summary period"-"Generated on:" lines.  If anything, this should<br /># be used to clean up in case an image was inserted with HTMLBody.<br /># As with HTMLHead, you can define as many of these as you want and<br /># they will be inserted in the output stream in order of apperance.<br /># Max string size is 80 characters.  Use multiple lines if you need to.<br /><br />HTMLPost         <BR CLEAR="all"><br /><br /># HTMLTail defines the HTML code to insert at the bottom of each<br /># HTML document, usually to include a link back to your home<br /># page or insert a small graphic.  It is inserted as a table<br /># data element (ie: <TD> your code here </TD>) and is right<br /># alligned with the page.  Max string size is 80 characters.<br /><br />HTMLTail <IMG SRC="msfree.png" ALT="100% Micro$oft free!"><br /><br /># HTMLEnd defines the HTML code to add at the very end of the<br /># generated files.  It defaults to what is shown below.  If<br /># used, you MUST specify the </BODY> and </HTML> closing tags<br /># as the last lines.  Max string length is 80 characters.<br /><br />HTMLEnd </BODY></HTML><br /><br /># The Quiet option suppresses output messages... Useful when run<br /># as a cron job to prevent bogus e-mails.  Values can be either<br /># "yes" or "no".  Default is "no".  Note: this does not suppress<br /># warnings and errors (which are printed to stderr).<br /><br />#Quiet                no<br /><br /># ReallyQuiet will supress all messages including errors and<br /># warnings.  Values can be 'yes' or 'no' with 'no' being the<br /># default.  If 'yes' is used here, it cannot be overriden from<br /># the command line, so use with caution.  A value of 'no' has<br /># no effect.<br /><br />#ReallyQuiet        no<br /><br /># TimeMe allows you to force the display of timing information<br /># at the end of processing.  A value of 'yes' will force the<br /># timing information to be displayed.  A value of 'no' has no<br /># effect.<br /><br />#TimeMe                no<br /><br /># GMTTime allows reports to show GMT (UTC) time instead of local<br /># time.  Default is to display the time the report was generated<br /># in the timezone of the local machine, such as EDT or PST.  This<br /># keyword allows you to have times displayed in UTC instead.  Use<br /># only if you really have a good reason, since it will probably<br /># screw up the reporting periods by however many hours your local<br /># time zone is off of GMT.<br /><br />#GMTTime                no<br /><br /># Debug prints additional information for error messages.  This<br /># will cause webalizer to dump bad records/fields instead of just<br /># telling you it found a bad one.   As usual, the value can be<br /># either "yes" or "no".  The default is "no".  It shouldn't be<br /># needed unless you start getting a lot of Warning or Error<br /># messages and want to see why.  (Note: warning and error messages<br /># are printed to stderr, not stdout like normal messages).<br /><br />#Debug                no<br /><br /># FoldSeqErr forces the Webalizer to ignore sequence errors.<br /># This is useful for Netscape and other web servers that cache<br /># the writing of log records and do not guarentee that they<br /># will be in chronological order.  The use of the FoldSeqErr<br /># option will cause out of sequence log records to be treated<br /># as if they had the same time stamp as the last valid record.<br /># Default is to ignore out of sequence log records.<br /><br />#FoldSeqErr        no<br /><br /># VisitTimeout allows you to set the default timeout for a visit<br /># (sometimes called a 'session').  The default is 30 minutes,<br /># which should be fine for most sites.<br /># Visits are determined by looking at the time of the current<br /># request, and the time of the last request from the site.  If<br /># the time difference is greater than the VisitTimeout value, it<br /># is considered a new visit, and visit totals are incremented.<br /># Value is the number of seconds to timeout (default=1800=30min)<br /><br />#VisitTimeout        1800<br /><br /># IgnoreHist shouldn't be used in a config file, but it is here<br /># just because it might be usefull in certain situations.  If the<br /># history file is ignored, the main "index.html" file will only<br /># report on the current log files contents.  Usefull only when you<br /># want to reproduce the reports from scratch.  USE WITH CAUTION!<br /># Valid values are "yes" or "no".  Default is "no".<br /><br />#IgnoreHist        no<br /><br /># Country Graph allows the usage by country graph to be disabled.<br /># Values can be 'yes' or 'no', default is 'yes'.<br /><br />#CountryGraph        yes<br /><br /># DailyGraph and DailyStats allows the daily statistics graph<br /># and statistics table to be disabled (not displayed).  Values<br /># may be "yes" or "no". Default is "yes".<br /><br />#DailyGraph        yes<br />#DailyStats        yes<br /><br /># HourlyGraph and HourlyStats allows the hourly statistics graph<br /># and statistics table to be disabled (not displayed).  Values<br /># may be "yes" or "no". Default is "yes".<br /><br />#HourlyGraph        yes<br />#HourlyStats        yes<br /><br /># GraphLegend allows the color coded legends to be turned on or off<br /># in the graphs.  The default is for them to be displayed.  This only<br /># toggles the color coded legends, the other legends are not changed.<br /># If you think they are hideous and ugly, say 'no' here :)<br /><br />#GraphLegend        yes<br /><br /># GraphLines allows you to have index lines drawn behind the graphs.<br /># I personally am not crazy about them, but a lot of people requested<br /># them and they weren't a big deal to add.  The number represents the<br /># number of lines you want displayed.  Default is 2, you can disable<br /># the lines by using a value of zero ('0').  [max is 20]<br /># Note, due to rounding errors, some values don't work quite right.<br /># The lower the better, with 1,2,3,4,6 and 10 producing nice results.<br /><br />#GraphLines        2<br /><br /># The "Top" options below define the number of entries for each table.<br /># Defaults are Sites=30, URL's=30, Referrers=30 and Agents=15, and<br /># Countries=30. TopKSites and TopKURLs (by KByte tables) both default<br /># to 10, as do the top entry/exit tables (TopEntry/TopExit).  The top<br /># search strings and usernames default to 20.  Tables may be disabled<br /># by using zero (0) for the value.<br /><br />#TopSites        30<br />#TopKSites       10<br />#TopURLs         30<br />#TopKURLs        10<br />#TopReferrers    30<br />#TopAgents       15<br />#TopCountries    30<br />#TopEntry        10<br />#TopExit         10<br />#TopSearch       20<br />#TopUsers        20<br /><br /># The All* keywords allow the display of all URL's, Sites, Referrers<br /># User Agents, Search Strings and Usernames.  If enabled, a seperate<br /># HTML page will be created, and a link will be added to the bottom<br /># of the appropriate "Top" table.  There are a couple of conditions<br /># for this to occur..  First, there must be more items than will fit<br /># in the "Top" table (otherwise it would just be duplicating what is<br /># already displayed).  Second, the listing will only show those items<br /># that are normally visable, which means it will not show any hidden<br /># items.  Grouped entries will be listed first, followed by individual<br /># items.  The value for these keywords can be either 'yes' or 'no',<br /># with the default being 'no'.  Please be aware that these pages can<br /># be quite large in size, particularly the sites page,  and seperate<br /># pages are generated for each month, which can consume quite a lot<br /># of disk space depending on the traffic to your site.<br /><br />#AllSites        no<br />#AllURLs        no<br />#AllReferrers        no<br />#AllAgents        no<br />#AllSearchStr        no<br />#AllUsers       no<br /><br /># The Webalizer normally strips the string 'index.' off the end of<br /># URL's in order to consolidate URL totals.  For example, the URL<br /># /somedir/index.html is turned into /somedir/ which is really the<br /># same URL.  This option allows you to specify additional strings<br /># to treat in the same way.  You don't need to specify 'index.' as<br /># it is always scanned for by The Webalizer, this option is just to<br /># specify _additional_ strings if needed.  If you don't need any,<br /># don't specify any as each string will be scanned for in EVERY<br /># log record... A bunch of them will degrade performance.  Also,<br /># the string is scanned for anywhere in the URL, so a string of<br /># 'home' would turn the URL /somedir/homepages/brad/home.html into<br /># just /somedir/ which is probably not what was intended.<br /><br />#IndexAlias     home.htm<br />#IndexAlias        homepage.htm<br /><br /># The Hide*, Group* and Ignore* and Include* keywords allow you to<br /># change the way Sites, URL's, Referrers, User Agents and Usernames<br /># are manipulated.  The Ignore* keywords will cause The Webalizer to<br /># completely ignore records as if they didn't exist (and thus not<br /># counted in the main site totals).  The Hide* keywords will prevent<br /># things from being displayed in the 'Top' tables, but will still be<br /># counted in the main totals.  The Group* keywords allow grouping<br /># similar objects as if they were one.  Grouped records are displayed<br /># in the 'Top' tables and can optionally be displayed in BOLD and/or<br /># shaded. Groups cannot be hidden, and are not counted in the main<br /># totals. The Group* options do not, by default, hide all the items<br /># that it matches.  If you want to hide the records that match (so just<br /># the grouping record is displayed), follow with an identical Hide*<br /># keyword with the same value.  (see example below)  In addition,<br /># Group* keywords may have an optional label which will be displayed<br /># instead of the keywords value.  The label should be seperated from<br /># the value by at least one 'white-space' character, such as a space<br /># or tab.<br />#<br /># The value can have either a leading or trailing '*' wildcard<br /># character.  If no wildcard is found, a match can occur anywhere<br /># in the string. Given a string "www.yourmama.com", the values "your",<br /># "*mama.com" and "www.your*" will all match.<br /><br /># Your own site should be hidden<br />#HideSite        *mrunix.net<br />#HideSite        localhost<br /><br /># Your own site gives most referrals<br />#HideReferrer        mrunix.net/<br /><br /># This one hides non-referrers ("-" Direct requests)<br />#HideReferrer        Direct Request<br /><br /># Usually you want to hide these<br />HideURL                *.gif<br />HideURL                *.GIF<br />HideURL                *.jpg<br />HideURL                *.JPG<br />HideURL                *.png<br />HideURL                *.PNG<br />HideURL                *.ra<br /><br /># Hiding agents is kind of futile<br />#HideAgent        RealPlayer<br /><br /># You can also hide based on authenticated username<br />#HideUser        root<br />#HideUser        admin<br /><br /># Grouping options<br />#GroupURL        /cgi-bin/*        CGI Scripts<br />#GroupURL        /images/*        Images<br /><br />#GroupSite        *.aol.com<br />#GroupSite        *.compuserve.com<br /><br />#GroupReferrer        yahoo.com/        Yahoo!<br />#GroupReferrer        excite.com/     Excite<br />#GroupReferrer        infoseek.com/   InfoSeek<br />#GroupReferrer        webcrawler.com/ WebCrawler<br /><br />#GroupUser      root            Admin users<br />#GroupUser      admin           Admin users<br />#GroupUser      wheel           Admin users<br /><br /># The following is a great way to get an overall total<br /># for browsers, and not display all the detail records.<br /># (You should use MangleAgent to refine further...)<br /><br />#GroupAgent        MSIE                Micro$oft Internet Exploder<br />#HideAgent        MSIE<br />#GroupAgent        Mozilla                Netscape<br />#HideAgent        Mozilla<br />#GroupAgent        Lynx*                Lynx<br />#HideAgent        Lynx*<br /><br /># HideAllSites allows forcing individual sites to be hidden in the<br /># report.  This is particularly useful when used in conjunction<br /># with the "GroupDomain" feature, but could be useful in other<br /># situations as well, such as when you only want to display grouped<br /># sites (with the GroupSite keywords...).  The value for this<br /># keyword can be either 'yes' or 'no', with 'no' the default,<br /># allowing individual sites to be displayed.<br /><br />#HideAllSites        no<br /><br /># The GroupDomains keyword allows you to group individual hostnames<br /># into their respective domains.  The value specifies the level of<br /># grouping to perform, and can be thought of as 'the number of dots'<br /># that will be displayed.  For example, if a visiting host is named<br /># cust1.tnt.mia.uu.net, a domain grouping of 1 will result in just<br /># "uu.net" being displayed, while a 2 will result in "mia.uu.net".<br /># The default value of zero disable this feature.  Domains will only<br /># be grouped if they do not match any existing "GroupSite" records,<br /># which allows overriding this feature with your own if desired.<br /><br />#GroupDomains        0<br /><br /># The GroupShading allows grouped rows to be shaded in the report.<br /># Useful if you have lots of groups and individual records that<br /># intermingle in the report, and you want to diferentiate the group<br /># records a little more.  Value can be 'yes' or 'no', with 'yes'<br /># being the default.<br /><br />#GroupShading        yes<br /><br /># GroupHighlight allows the group record to be displayed in BOLD.<br /># Can be either 'yes' or 'no' with the default 'yes'.<br /><br />#GroupHighlight        yes<br /><br /># The Ignore* keywords allow you to completely ignore log records based<br /># on hostname, URL, user agent, referrer or username.  I hessitated in<br /># adding these, since the Webalizer was designed to generate _accurate_<br /># statistics about a web servers performance.  By choosing to ignore<br /># records, the accuracy of reports become skewed, negating why I wrote<br /># this program in the first place.  However, due to popular demand, here<br /># they are.  Use the same as the Hide* keywords, where the value can have<br /># a leading or trailing wildcard '*'.  Use at your own risk ;)<br /><br />#IgnoreSite        bad.site.net<br />#IgnoreURL        /test*<br />#IgnoreReferrer        file:/*<br />#IgnoreAgent        RealPlayer<br />#IgnoreUser     root<br /><br /># The Include* keywords allow you to force the inclusion of log records<br /># based on hostname, URL, user agent, referrer or username.  They take<br /># precidence over the Ignore* keywords.  Note: Using Ignore/Include<br /># combinations to selectivly process parts of a web site is _extremely<br /># inefficent_!!! Avoid doing so if possible (ie: grep the records to a<br /># seperate file if you really want that kind of report).<br /><br /># Example: Only show stats on Joe User's pages...<br />#IgnoreURL        *<br />#IncludeURL        ~joeuser*<br /><br /># Or based on an authenticated username<br />#IgnoreUser     *<br />#IncludeUser    someuser<br /><br /># The MangleAgents allows you to specify how much, if any, The Webalizer<br /># should mangle user agent names.  This allows several levels of detail<br /># to be produced when reporting user agent statistics.  There are six<br /># levels that can be specified, which define different levels of detail<br /># supression.  Level 5 shows only the browser name (MSIE or Mozilla)<br /># and the major version number.  Level 4 adds the minor version number<br /># (single decimal place).  Level 3 displays the minor version to two<br /># decimal places.  Level 2 will add any sub-level designation (such<br /># as Mozilla/3.01Gold or MSIE 3.0b).  Level 1 will attempt to also add<br /># the system type if it is specified.  The default Level 0 displays the<br /># full user agent field without modification and produces the greatest<br /># amount of detail.  User agent names that can't be mangled will be<br /># left unmodified.<br /><br />#MangleAgents    0<br /><br /># The SearchEngine keywords allow specification of search engines and<br /># their query strings on the URL.  These are used to locate and report<br /># what search strings are used to find your site.  The first word is<br /># a substring to match in the referrer field that identifies the search<br /># engine, and the second is the URL variable used by that search engine<br /># to define it's search terms.<br /><br />SearchEngine        yahoo.com        p=<br />SearchEngine        altavista.com        q=<br />SearchEngine        google.com        q=<br />SearchEngine        eureka.com        q=<br />SearchEngine        lycos.com        query=<br />SearchEngine        hotbot.com        MT=<br />SearchEngine        msn.com                MT=<br />SearchEngine        infoseek.com        qt=<br />SearchEngine        webcrawler        searchText=<br />SearchEngine        excite                search=<br />SearchEngine        netscape.com        search=<br />SearchEngine        mamma.com        query=<br />SearchEngine        alltheweb.com        query=<br />SearchEngine        northernlight.com  qr=<br /><br /># The Dump* keywords allow the dumping of Sites, URL's, Referrers<br /># User Agents, Usernames and Search strings to seperate tab delimited<br /># text files, suitable for import into most database or spreadsheet<br /># programs.<br /><br /># DumpPath specifies the path to dump the files.  If not specified,<br /># it will default to the current output directory.  Do not use a<br /># trailing slash ('/').<br /><br />#DumpPath        /var/lib/httpd/logs<br /><br /># The DumpHeader keyword specifies if a header record should be<br /># written to the file.  A header record is the first record of the<br /># file, and contains the labels for each field written.  Normally,<br /># files that are intended to be imported into a database system<br /># will not need a header record, while spreadsheets usually do.<br /># Value can be either 'yes' or 'no', with 'no' being the default.<br /><br />#DumpHeader        no<br /><br /># DumpExtension allow you to specify the dump filename extension<br /># to use.  The default is "tab", but some programs are pickey about<br /># the filenames they use, so you may change it here (for example,<br /># some people may prefer to use "csv").<br /><br />#DumpExtension        tab<br /><br /># These control the dumping of each individual table.  The value<br /># can be either 'yes' or 'no'.. the default is 'no'.<br /><br />#DumpSites        no<br />#DumpURLs        no<br />#DumpReferrers        no<br />#DumpAgents        no<br />#DumpUsers        no<br />#DumpSearchStr  no<br /><br /># End of configuration file...  Have a nice day! </dd> <dt class="postheader"> Název: <strong>webalizer na ubuntu dapper serveru - problem s cestinou</strong><br /> Přispěvatel: <strong>CHACAL</strong> <strong>17 Května 2007, 22:14:01</strong> </dt> <dd class="postbody"> Spis bych si tip, ze to je problem webalizeru - resp jeho detekovani jazyka. mam stejnej problem a kdyz sem tam lez z anglickejch win, tak to slo anglicky, tudiz ok :-) - az se budu nudit, prozkoumam konfigurak, jestli by to neslo udelat natvrdo v anglictine. </dd> </dl> <div id="footer" class="smalltext"> <span class="smalltext" style="display: inline; visibility: visible; font-family: Verdana, Arial, sans-serif;"><a href="https://forum.ubuntu.cz/index.php?action=credits" title="Simple Machines Forum" target="_blank" class="new_win">SMF 2.0.19</a> | <a href="http://www.simplemachines.org/about/smf/license.php" title="License" target="_blank" class="new_win">SMF © 2016</a>, <a href="http://www.simplemachines.org" title="Simple Machines" target="_blank" class="new_win">Simple Machines</a> </span> </div> </body> </html>