📄 readme
字号:
your own web server to be hidden, as it is usually the top generator of references to your own pages. Of course, this keyword is useless if 1) your log file does not include referrer information or 2) you disable the top referrers table. Command line argument: -r HideSite This allows you to hide specified sites from the "Top Sites" table. Normally, you would only specify your own web server or other local machines to be hidden, as they are usually the highest hitters of your web site, especially if you have their browsers home page pointing to it. Command line argument: -s HideAllSites This allows hiding all indvidual sites from the display, which can be useful when a lot of groupings are being used (since grouped records cannot be hidden). It is particularly useful in conjunction with the GroupDomain feature, however can be useful in other situations as well. Value can be either 'yes' or 'no', with 'no' the default. Command line argument: -XHideURL This allows you to hide URL's from the "Top URL's" table. Normally, this is used to hide items such as graphic files, audio files or other 'non-html' files that are transferred to the visiting user. Command line argument: -u HideUser This allows you to hide Usernames from the "Top Usernames" table. Usernames are only available if you use http based authentication on your web server.Group Object Keywords---------------------The Group* keywords allow object grouping based on Site, URL, Referrer,User Agent and Usernames. Combined with the Hide* keywords, you cancustomize exactly what will be displayed in the 'Top' tables. For example,to only display totals for a particular directory, use a GroupURL andHideURL with the same value (ie: '/help/*'). Group processing is onlydone after the individual record has been fully processed, so name manglingand site total updates have already been performed. Because of this, groupsare not counted in the main site total (as that would cause duplication).Groups can be displayed in bold and shaded as well. Grouped records arenot, by default, hidden from the report. This allows you to display agrouped total, while still being able to see the individual records, evenif they are part of the group. If you want to hide the detail records,follow the Group* directive with a Hide* one using the same value. Thereare no command line switches for these keywords. The Group* keywords alsoaccept an optional label to be displayed instead of the actual value used.This label should be separated from the value by at least one whitespacecharacter, such as a space or tab character. See the sample.conf filefor examples.GroupReferrer Allows grouping Referrers. Can be handy for some of the major search engines that have multiple host names a referral could come from.GroupURL This keyword allows grouping URL's. Useful for grouping complete directory trees.GroupSite This keywords allows grouping Sites. Most used for grouping top level domains and unresolved IP address for local dial-ups, etc...GroupAgent Groups User Agents. A handy example of how you could use this one is to use "Mozilla" and "MSIE" as the values for GroupAgent and HideAgent keywords. Make sure you put the "MSIE" one first.GroupDomains Allows automatic grouping of domains. The numeric value represents the level of grouping, and can be thought of as 'the number of dots' to display. A 1 will display second level domains only (xxx.xxx), a 2 will display third level domains (xxx.xxx.xxx) etc... The default value of 0 disables any domain grouping. Command line argument: -gGroupUser Allows grouping of usernames. Combined with a group name, this can be handy for displaying statistics on a particular group of users without displaying their real usernames.GroupShading Allows shading of table rows for groups. Value can be 'yes' or 'no', with the default being 'yes'.GroupHighlight Allows bolding of table rows for groups. Value can be 'yes' or 'no', with the default being 'yes'.Ignore/Include Object Keywords----------------------These keywords allow you to completely ignore log records when generatingstatistics, or to force their inclusion regardless of ignore criteria.Records can be ignored or included based on site, URL, user agent, referrerand username. Be aware that by choosing to ignore records, the accuracy ofthe generated statistics become skewed, making it impossible to producean accurate representation of load on the web server. These keywordsbehave identical to the Hide* keywords above, where the value can havea leading or trailing wildcard '*'. These keywords, like the Hide* ones,have an absolute limit of 80 characters for their values. These keywordsdo not have any command line switch counterparts, so they may only bespecified in a configuration file. It should also be pointed out thatusing the Ignore/Include combination to selectively exclude an entiresite while including a particular 'chunk' is _extremely_ inefficient,and should be avoided. Try grep'ing the records into a separate fileand process it instead.IgnoreSite This allows specified sites to be completely ignored from the generated statistics.IgnoreURL This allows specified URL's to be completely ignored from the generated statistics. One use for this keyword would be to ignore all hits to a 'temporary' directory where development work is being done, but is not accessible to the outside world.IgnoreReferrer This allows records to be ignored based on the referrer field.IgnoreAgent This allows specified User Agent records to be completely ignored from the statistics. Maybe useful if you really don't want to see all those hits from MSIE :)IgnoreUser This allows specified username records to be completely ignored from the statistics. Usernames can only be used if you use http authentication on your server.IncludeSite Force the record to be processed based on hostname. This takes precedence over the Ignore* keywords.IncludeURL Force the record to be processed based on URL. This takes precedence over the Ignore* keywords.IncludeReferrer Force the record to be processed based on referrer. This takes precedence over the Ignore* keywords.IncludeAgent Force the record to be processed based on user agent. This takes precedence over the Ignore* keywords.IncludeUser Force the record to be processed based on username. Usernames are only available if you use http based authentication on your server. This takes precedence over the Ignore* keywords.Dump Object Keywords--------------------The Dump* Keywords allow text files to be generated that can then be usedfor import into most database, spreadsheet and other external programs.The file is a standard tab delimited text file, meaning that each columnis separated by a tab (0x09) character. A header record may be includedif required, using the 'DumpHeader' keyword. Since these files containall records that have been processed, including normally hidden records,an alternate location for the files can be specified using the 'DumpPath'keyword, otherwise they will be located in the default output directory.DumpPath Specifies an alternate location for the dump files. The default output location will be used otherwise. The value is the path portion to use, and normally should be an absolute path (ie: has a leading '/' character), however relative path names can be used as well, and will be relative to the output directory location.DumpExtension Allows the dump filename extensions to be specified. The default extension is "tab", however may be changed with this option.DumpHeader Allows a header record to be written as the first record of the file. Value can be either 'yes' or 'no', with the default being 'no'.DumpSites Dump tab delimited sites file. Value can be either 'yes' or 'no', with the default being 'no'. The filename used is site_YYYYMM.tab (YYYY=year, MM=month).DumpURLs Dump tab delimited url file. Value can be either 'yes' or 'no', with the default being 'no'. The filename used is url_YYYYMM.tab (YYYY=year, MM=month).DumpReferrers Dump tab delimited referrer file. Value can be either 'yes' or 'no', with the default being 'no'. Filename used is ref_YYYYMM.tab (YYYY=year, MM=month). Referrer information is only available if present in the log file (ie: combined web server log).DumpAgents Dump tab delmited user agent file. Value can be either 'yes' or 'no', with the default being 'no'. Filename used is agent_YYYYMM.tab (YYYY=year, MM=month). User agent information is only available if present in the log file (ie: combined web server log).DumpUsers Dump tab delimited username file. Value can be either 'yes' or 'no', with the default being 'no'. FIlename used is user_YYYYMM.tab (YYYY=year, MM=month). The username data is only avilable if processing a wu-ftpd xferlog or http authentication is used on the web server and that information is present in the log.DumpSearchStr Dump tab delimited search string file. Value can be either 'yes' or 'no', with the default being 'no'. Filename used is search_YYYYMM.tab (YYYY=year, MM=month). the search string data is only available if referrer information is present in the log being processed and recognized search engines were found and processed.HTML Generation Keywords------------------------These keywords allow you to customize the HTML code that The Webalizerproduces, such as adding a corporate logo or links to other web pages.You can specify as many of these keywords as you like, and they will beused in the order that they are found in the file. Values cannot exceed80 characters in length, so you may have to break long lines up into twoor more lines. There are no command line counterparts to these keywords.HTMLExtension Allows generated pages to use something other than the default 'html' extension for the filenames. Do not include the leading period ('.') when you specify the extension. Command line argument: -xHTMLPre Allows code to be inserted at the very beginning of the HTML files. Defaults to the standard HTML 3.2 DOCTYPE record. Be careful not to include any HTML here, as it is inserted _before_ the <HTML> tag in the file. Use it for server-side scripting capabilities, such as php3, to insert scripting files and other directives.HTMLHead Allows you to insert HTML code between the <HEAD></HEAD> block. There is no default. Useful for adding scripts to the HTML page, such as Javascript or php3, or even just for adding a few META tags to the document.HTMLBody This keyword defines HTML code to be placed immediately after the <HEAD> section of the report, just before the title and "summary period/generated on" lines. If used, the first HTMLHead line MUST include a <BODY> tag. Put whatever else you want in subsequent lines, but keep in mind the placement of this code in relation to the title and other aspects
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -