📄 1163-1164.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:File Formats:EarthWeb Inc.-</TITLE>
</HEAD>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!-- ISBN=0672311046 //-->
<!-- TITLE=Linux Complete Command Reference//-->
<!-- AUTHOR=Red Hat//-->
<!-- PUBLISHER=Macmillan Computer Publishing//-->
<!-- IMPRINT=Sams//-->
<!-- CHAPTER=05 //-->
<!-- PAGES=1103-1208 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="1161-1162.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1165-1166.html">Next</A></CENTER></P>
<A NAME="PAGENUM-1163"><P>Page 1163</P></A>
<!-- CODE //-->
<PRE>
uunet.uu.net/uunet:!ne.*/world,usa,na,foo,ddn,gnu,inet\
:Tm:nntpfunnel1
nntpfunnel1:!*\
:Tc,Wmn*:/nntpfanout
## A UUCP site that wants comp.* and moderated soc groups
uucpsite!comp:!*,comp.*/world,usa,na,gnu\
:Tm:uucpsite
uucpsite!soc:!*,soc.*/world,usa,na,gnu\
:Tm,Nm:uucpsite
uucpsite:!*\
:Tf,Wfb:/usr/spool/batch/uucpsite
</PRE>
<!-- END CODE //-->
<P>The last two sets of entries show how funnel feeds can be used. For example, the
nntpfanout program would receive lines like the following on its standard input:
</P>
<!-- CODE SNIP //-->
<PRE>
<123@litchi.foo.com> comp/sources/unix/888 nic.near.net uunet.uu.net
<124@litchi.foo.com> ne/general/1003 nic.near.net
</PRE>
<!-- END CODE SNIP //-->
<P>Because the UUCP funnel is only destined for one site, the asterisk is not needed and entries like the following will
be written into the file:
</P>
<!-- CODE SNIP //-->
<PRE>
<qwe#37x@snark.uu.net>comp/society/folklore/3
<123@litchi.foo.com> comp/sources/unix/888
</PRE>
<!-- END CODE SNIP //-->
<P><B>
HISTORY
</B></P>
<P>Written by Rich $alz (rsalz@uunet.uu.net) for InterNetNews.
</P>
<P><B>
SEE ALSO
</B></P>
<P>
active(5), buffchan(8), ctlinnd(8), innd(8), wildmat(3)
</P>
<H3><A NAME="ch05_ 36">
newslog
</A></H3>
<P>
newslog—Description of Usenet log files.
</P>
<P><B>
DESCRIPTION
</B></P>
<P>Most log files created by Usenet programs reside in the
/var/log/news directory and have a .log extension. Several
versions are usually kept with an additional extension such as
.1, .2, and so on; the higher the number, the older the log. The
older versions are compressed.
</P>
<P>The scanlogs script and related utilities (see
newslog(8)) are responsible for rotating and compressing these files.
</P>
<P>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
innstat script (see newslog(8)) monitors the size of all log files.
</P>
<P>The following files will only accumulate data under the direction of
control.ctl(5):
</P>
<!-- CODE SNIP //-->
<PRE>
control.log, miscctl.log, newgroup.log, rmgroup.log, unwanted.log
</PRE>
<!-- END CODE SNIP //-->
<P>In order to create these files, the message and
action fields of control.ctl should be chosen from the following table:
</P>
<TABLE>
<TR><TD>
Message
</TD><TD>
Action
</TD><TD>
Meaning
</TD></TR><TR><TD>
all
</TD><TD>
log=miscctl
</TD><TD>
Log all messages by default
</TD></TR><TR><TD>
default
</TD><TD>
log=miscctl
</TD><TD>
Log unknown messages
</TD></TR><TR><TD>
newgroup
</TD><TD>
doit=newgroup
</TD><TD>
Create group and log message
</TD></TR><TR><TD>
newgroup
</TD><TD>
log=newgroup
</TD><TD>
Log message
</TD></TR></TABLE>
<P>
Continues
</P>
<A NAME="PAGENUM-1164"><P>Page 1164</P></A>
<TABLE>
<TR><TD>
Message
</TD><TD>
Action
</TD><TD>
Meaning
</TD></TR><TR><TD>
rmgroup
</TD><TD>
doit=rmgroup
</TD><TD>
Remove group and log message
</TD></TR><TR><TD>
rmgroup
</TD><TD>
log=rmgroup
</TD><TD>
Log message
</TD></TR><TR><TD>
"other"
</TD><TD>
doit=miscctl
</TD><TD>
Log and process the message
</TD></TR><TR><TD>
"other"
</TD><TD>
log=miscctl
</TD><TD>
Log message
</TD></TR></TABLE>
<P>Here, "other" refers to any other control message such as:
</P>
<!-- CODE SNIP //-->
<PRE>
checkgroups ihave sendme sendsys senduuname version
</PRE>
<!-- END CODE SNIP //-->
<P>The following is a list of log files.
</P>
<TABLE>
<TR><TD>
control.log
</TD><TD>
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 identical
arguments, regardless of whether they were actually processed. All control arguments, including
invalid ones, are counted. This file is updated by
tally.control, which is invoked by scanlogs if either the
newgroup or rmgroup logs exist. This file is not rotated.
</TD></TR><TR><TD>
errlog
</TD><TD>
This file contains the standard output and standard error of any program spawned
by innd(8). The most common programs are the control-message handlers found in
/news/bin/control. This file should be empty. Scanlogs will print the entire contents of this log file if
it is non-empty.
</TD></TR><TR><TD>
expire.log
</TD><TD>
By default, when news.daily is going to expire old news articles, it writes the date to
this file, followed by any output from expire(8) and the ending date. All lines but the first
are indented four spaces.
</TD></TR><TR><TD>
miscctl.log
</TD><TD>
When control.ctl is configured as described above, all control messages except
newgroup and rmgroup are appended to this file by
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.
</TD></TR><TR><TD>
newgroup.log
</TD><TD>
When control.ctl is configured as described above, all
newgroup messages are appended to this file using the same format as for
miscctl.log.
</TD></TR><TR><TD>
news
</TD><TD>
This file logs articles received by
innd. scanlogs summarizes the rejected articles reported
in this file.
</TD></TR><TR><TD>
news.crit
</TD><TD>
All critical error messages issued by
innd are appended to this file via syslog(3). This log
file should be empty. scanlogs will print the entire contents of this log file if it is
non-empty. You should have the following line in your
syslog.conf(5) file:
</TD></TR><TR><TD>
</TD><TD>
<!-- CODE SNIP //-->
<PRE>
news.crit /var/log/news/news.crit
</PRE>
<!-- END CODE SNIP //-->
</TD></TR><TR><TD>
news.err
</TD><TD>
All major error messages issued by
innd are appended to this file via syslog. This log
file should be empty. scanlogs will print the entire contents of this log file if it is
non-empty. You should have the following line in your
syslog.conf file:
</TD></TR><TR><TD>
</TD><TD>
<!-- CODE SNIP //-->
<PRE>
news.err /var/log/news/news.err
</PRE>
<!-- END CODE SNIP //-->
</TD></TR><TR><TD>
news.notice
</TD><TD>
All standard error messages and status messages issued by
innd are appended to this file via syslog.
scanlogs uses the awk(1) script innlog.awk to summarize this file. You should
have the following line in your syslog.conf file:
</TD></TR><TR><TD>
</TD><TD>
<!-- CODE SNIP //-->
<PRE>
news.notice /var/log/news/news.notice
</PRE>
<!-- END CODE SNIP //-->
</TD></TR><TR><TD>
nntpsend.log
</TD><TD>
The nntpsend(8) programs appends all status messages to this file.
</TD></TR><TR><TD>
rmgroup.log
</TD><TD>
When control.ctl is configured as described previously, all rmgroup messages are
appended to this file using the same format as for
miscctl.log.
</TD></TR><TR><TD>
unwanted.log
</TD><TD>
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 tally.unwanted and maintained in reverse numeric order (the most popular rejected
group first). This file is not rotated.
</TD></TR></TABLE>
<P><CENTER>
<a href="1161-1162.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1165-1166.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -