.TH NEWSLOG 5 .SH NAME newslog \- description of Usenet log files .SH DESCRIPTION Most log files created by Usenet programs reside in the .I directory and have a ``.log'' extension. Several versions are usually kept with an additional extension such as ``.1'', ``.2'', etc. \(em the higher the number, the older the log. The older versions may be compressed and thus may have a ``.1.gz'', ``.2.gz'', etc. extension. .PP The .I scanlogs script and related utilities (see .IR scanlogs (8)) are responsible for rotating and compressing these files. .PP Some log files always have data, others only have data if there is a problem, and others are only created if a particular program is used or configuration parameter is set. The .I innstat script (see .IR innstat (8)) monitors the size of all log files. .PP The following files will only accumulate data under the direction of .IR control.ctl (5): .sp 1 .RS control.log miscctl.log newgroup.log rmgroup.log unwanted.log .RE .sp 1 In order to create these files, the ``message'' and ``action'' fields of .I control.ctl should be chosen from the following table: .sp 1 .RS .nf .ta \w'newgroup 'u +\w'doit=newgroup 'u Message Action Meaning all log=miscctl Log all messages by default default log=miscctl Log unknown messages newgroup doit=newgroup Create group and log message newgroup log=newgroup Log message rmgroup doit=rmgroup Remove group and log message rmgroup log=rmgroup Log message ``other'' doit=miscctl log and process the message ``other'' log=miscctl Log message .fi .RE .sp 1 Here, ``other'' refers to any other control message such as: .sp 1 .RS .nf checkgroups ihave sendme sendsys senduuname version .fi .RE .PP The following is a list of log files: .TP .I control.log This file maintains a count of the number of newgroup and rmgroup control messages seen for each newsgroup. The count is of the number of control messages with the indicated arguments, regardless if they were actually processed. All control arguments, including invalid ones, are counted. This file is updated by .IR tally.control , which is invoked by .I scanlogs if either the newgroup or rmgroup logs exist. This file is not rotated. .TP .I errlog This file contains the standard output and standard error of any program spawned by .IR innd (8), such as channel feeds configured in .IR newsfeeds . This file should normally be empty. .I Scanlogs will print the entire contents of this log file if it is non-empty. .TP .I expire.log By default, when .I news.daily is going to expire old news articles, it writes the date to this file, followed by any output from .IR expire (8) and the ending date. All lines but the first are indented four spaces. .TP .I miscctl.log When .I control.ctl is configured as described above, all control messages except newgroup and rmgroup are appended to this file by .IR writelog . There will be a summary line describing the message and the action taken, followed by the article indented by four spaces, and a blank line. .TP .I newgroup.log When .I control.ctl is configured as described above, all newgroup messages are appended to this file using the same format as for .IR miscctl.log . .TP .I news This file logs articles received by .IR innd . .I Scanlogs summarizes the rejected articles reported in this file. .TP .I news.crit All critical error messages issued by .I innd are appended to this file via .IR syslog (3). This log file should be empty. .I Scanlogs will print the entire contents of this log file if it is non-empty. You should have the following line in your system .I syslog.conf file, using a tab character for the delimiter: .sp 1 .RS .RS news.crit /news.crit .RE .RE .sp 1 (A typical entry is shown; it should agree with .I .) .TP .I news.err All major error messages issued by .I innd are appended to this file via .IR syslog (3). This log file should be empty. .I Scanlogs will print the entire contents of this log file if it is non-empty. You should have the following line in your system .I syslog.conf file, using a tab character for the delimiter: .sp 1 .RS .RS news.err /news.err .RE .RE .sp 1 (A typical entry is shown; it should agree with .I .) .TP .I news.notice All standard error messages and status messages issued by .I innd are appended to this file via .IR syslog (3). .I Scanlogs uses the .IR perl (1) script .IR innreport (8) to summarize this file. You should have the following line in your system .I syslog.conf file, using a tab character for the delimiter: .sp 1 .RS .RS news.notice /news.notice .RE .RE (A typical entry is shown; it should agree with .I .) .TP .I nntpsend.log The .IR nntpsend (8) programs appends all status messages to this file. .TP .I rmgroup.log When .I control.ctl is configured as described above, all rmgroup messages are appended to this file using the same format as for .IR miscctl.log . .TP .I unwanted.log This log maintains a count of the number of articles that were rejected because they were posted to newsgroups that do not exist at the local site. This file is updated by .I tally.unwanted and maintained in reverse numeric order (the most popular rejected group first). This file is not rotated. .SH HISTORY Written by Landon Curt Noll and Rich $alz for InterNetNews. .de R$ This is revision \\$3, dated \\$4. .. .R$ $Id: newslog.5 6398 2003-07-12 19:15:50Z rra $ .SH "SEE ALSO" control.ctl(5), ctlinnd(8), expire(8), inn.conf(5), innd(8), news.daily(8), nntpsend(8), syslog.conf(5).