📄 1103-1106.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="../ch04/1102-1102.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1107-1108.html">Next</A></CENTER></P>
<A NAME="PAGENUM-1103"><P>Page 1103</P></A>
<H3><A NAME="ch05_ 1">
Part V:
</A></H3>
<H2>
File Formats
</H2>
<A NAME="PAGENUM-1104"><P>Page 1104</P></A>
<H3><A NAME="ch05_ 2">
intro
</A></H3>
<P>intro—Introduction to file formats.
</P>
<P><B>
DESCRIPTION
</B></P>
<P>This chapter describes various file formats and protocols, and the used C structures, if any.
</P>
<P><B>
AUTHORS
</B></P>
<P>Look at the header of the manual page for the authors and copyright conditions. Note that these can be different from
page to page!
</P>
<P>Linux, 24 July 1993
</P>
<H3><A NAME="ch05_ 3">
active, active.times
</A></H3>
<P>active, active.times—List of active Usenet newsgroups.
</P>
<P><B>
DESCRIPTION
</B></P>
<P>The file /news/lib/active lists the newsgroups that the local site receives. Each newsgroup should be listed only once.
Each line specifies one group; their order in the file does not matter. Within each newsgroup, articles are assigned unique
names, which are monotonically increasing numbers.
</P>
<P>If an article is posted to newsgroups not mentioned in this file, those newsgroups are ignored. If no valid newsgroups
are specified, the article is filed into the newsgroup "junk" and only propagated to sites that receive the "junk" newsgroup.
</P>
<P>Each line consists of four fields specified by a space:
</P>
<!-- CODE SNIP //-->
<PRE>
name himark lomark flags
</PRE>
<!-- END CODE SNIP //-->
<P>The first field is the name of the newsgroup. Newsgroups that start with the three characters
to. are treated specially; see innd(8). The second field is the highest article number that has been used in that newsgroup. The third field is the
lowest article number in the group; this number is not guaranteed to be accurate and should only be taken as a hint. Note
that because of article cancellations, there may be gaps in the numbering sequence. If the lowest article number is greater than
the highest article number, there are no articles in the newsgroup. To make it possible to update an entry in-place
without rewriting the entire file, the second and third fields are padded with leading zeros to make them a fixed width.
</P>
<P>The fourth field can contain one of the following flags:
</P>
<TABLE>
<TR><TD>
y
</TD><TD>
Local postings are allowed
</TD></TR><TR><TD>
n
</TD><TD>
No local postings are allowed, only remote ones
</TD></TR><TR><TD>
m
</TD><TD>
The group is moderated and all postings must be approved
</TD></TR><TR><TD>
j
</TD><TD>
Articles in this group are not kept but only passed on
</TD></TR><TR><TD>
x
</TD><TD>
Articles cannot be posted to this newsgroup
</TD></TR><TR><TD>
=foo.bar
</TD><TD>
Articles are locally filed into the foo.bar group
</TD></TR></TABLE>
<P>If a newsgroup has the j flag, then no articles will be filed into that newsgroup and local postings to that group should not
be generated. If an article for such a newsgroup is received from a remote site, it will be filed into the "junk" newsgroup if it
is not cross-posted. This is different from not having a newsgroup listed in the file because sites can subscribe to
j newsgroups and the article will be propagated to them.
</P>
<P>If the fourth field of a newsgroup starts with an equal sign, then the newsgroup is an alias. Articles can be posted to the
group but will be treated as if they were posted to the group named after the equal sign. The second and third fields are
ignored. Note that the newsgroup header is not modified (Alias groups are typically used during a transition and are typically
created with ctlinnd(8)). An alias newsgroup should not point to another alias.
</P>
<A NAME="PAGENUM-1105"><P>Page 1105</P></A>
<P>The file /news/lib/active.times provides a chronological record of when newsgroups are created. This file is
normally updated by innd(8) whenever a ctlinnd
newgroup command is done. Each line consist of three fields:
</P>
<!-- CODE SNIP //-->
<PRE>
name time creator
</PRE>
<!-- END CODE SNIP //-->
<P>The first field is the name of the newsgroup. The second field is the time it was created, expressed as the number of
seconds since the epoch—a time_t; see
gettimeofday(2). The third field is the electronic mail address of the person who created
the group.
</P>
<P><B>
HISTORY
</B></P>
<P>
Written by Rich $alz (rsalz@uunet.uu.net) for InterNetNews.
</P>
<P><B>
SEE ALSO
</B></P>
<!-- CODE SNIP //-->
<PRE>
ctlinnd(8), innd(8)
</PRE>
<!-- END CODE SNIP //-->
<H3><A NAME="ch05_ 4">
adduser.conf
</A></H3>
<P>
adduser.conf—Configuration file for adduser(8) and add group(8).
</P>
<P><B>
SYNOPSIS
</B></P>
<P>/etc/adduser.conf</P>
<P><B>
DESCRIPTION
</B></P>
<P>The file adduser.conf contains defaults for the programs
adduser(8) and addgroup(8). Each option takes the form
option = value.
</P>
<P>The valid configuration options are</P>
<TBL>
<COLS=2>
<C>
DSHELL
<C>
The login shell to be used for all new users. Defaults to
/bin/bash.
<C>
DHOME
<C>
The directory in which new home directories should be created. Defaults to
/home.
<C>
SKEL
<C>
The directory from which skeletal user configuration files should be copied. Defaults to
/etc/skel.
<C>
FIRST_UID
<C>
Specifies the lowest valid UID for normal users on your system. IDs below
FIRST_UID are reserved for administrative and system accounts. Defaults to
1000.
<C>
USERGROUPS
<C>
The USERGROUPS variable can be either
yes or no. If yes, each created user will be given
their own group to use as a default, and their setup will arrange to have them create files
group-writable by default, thus allowing them to effectively use group-writeable filespace
areas (such as /usr/local). If no, each created user will be placed in the group whose GID
is USERS_GID, and they will create files not group-writeable by default.
<C>
USERS_GID
<C>
If USERGROUPS is no, then USERS_GID is the GID given to all newly created users. The
default value is 100.
</TBL>
<P><B>
FILES
</B></P>
<P>/etc/adduser.conf</P>
<P><B>
SEE ALSO
</B></P>
<P>adduser(8)</P>
<P>Debian GNU/Linux version 1.94</P>
<A NAME="PAGENUM-1106"><P>Page 1106</P></A>
<H3>
aliases
</H3>
<P>aliases—Aliases file for sendmail.</P>
<P><B>
SYNOPSIS
</B></P>
<P>aliases</P>
<P><B>
DESCRIPTION
</B></P>
<P>
This file describes user ID aliases used by . The file resides in and is formatted as a series of lines of the form:
</P>
<PRE>
name: name_1, name_2, name_3, ...
</PRE>
<P>
The name is the name to alias, and the name_n are the aliases for that name. Lines beginning with whitespace are
continuation lines. Lines beginning with # are comments.
</P>
<P>
Aliasing occurs only on local names. Loops cannot occur because no message will be sent to any person more than once.
</P>
<P>After aliasing has been done, local and valid recipients who have a
.forward file in their home directory have
messages forwarded to the list of users defined in that file.
</P>
<P>This is only the raw data file; the actual aliasing information is placed into a binary format in the files and using the
program newaliases(1). A newaliases command should be executed each time the aliases file is changed for the change to take effect.
</P>
<P><B>
SEE ALSO
</B></P>
<P>
newaliases(1), dbm(3), sendmail(8), "Sendmail Installation and Operation Guide," "Sendmail: An Internetwork
Mail Router."
</P>
<P><B>
BUGS
</B></P>
<P>
Because of restrictions in dbm(3), a single alias cannot contain more than about 1000 bytes of information. You can get
longer aliases by "chaining"—that is, making the last name in the alias a dummy name that is a continuation alias.
</P>
<P><B>
HISTORY
</B></P>
<P>The aliases file format appeared in BSD 4.0.</P>
<P>BSD 4, 10 May 1991</P>
<H3>
cfingerd
</H3>
<P>
cfingerd—Configurable finger daemon.
</P>
<P><B>
SYNOPSIS
</B></P>
<P>cfingerd [_c|_d|_e|_o|_v]</P>
<TBL>
<COLS=2>
<C>
_c
<C>
Check configuration
<C>
_d
<C>
Run as daemon, not inetd
<C>
_e
<C>
Emulate local finger without inetd
<C>
_o
<C>
Turn off all finger queries
<C>
_v
<C>
Request version information
</TBL>
<P>_c checks your installed configuration. This makes sure there are no existing errors in the current
cfingerd.conf file.
</P>
<P>_d runs cfingerd as a daemon. Don't run
cfingerd this way if you're using inetd.
</P>
<P>_e allows you to emulate a local finger on a user that exists on your system. This makes it so that you can test
cfingerd on your system before installing it. Using the
_e directive is the same as installing the software, typing
finger username@ and getting the output. Using _e
username does the same.
</P>
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -