ACTIVE (5)

DESCRIPTION

The file <pathdb in inn.conf>/_PATH_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.

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 either filed into the newsgroup ``junk'' and only propagated to sites that receive the ``junk'' newsgroup or it is ignored completely, depending on the ``wanttrash'' option in inn.conf (5)

Each line consists of four fields specified by a space:

        name himark lomark flag

The first field is the name of the newsgroup. If <mergetogroups in inn.conf> is ``true'', 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 to be a hint. Note that because of article cancellations, there may be gaps in the numbering sequence. If the lowest article number is greater then the highest article number, then there are no articles in the newsgroup. In order to make it possible to update an entry in-place without rewriting the entire file, the second and third fields are padded out with leading zeros to make them a fixed width.

The fourth field can contain one of the following flags:

\w'=foo.bar   'u
y        Local postings are allowed
n        No local postings are allowed, only remote ones
m        The group is moderated and all postings must be approved
j        Articles in this group are not kept, but only passed on
x        Articles cannot be posted to this newsgroup
=foo.bar Articles are locally filed into the ``foo.bar'' group

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.

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.

The file <pathdb in inn.conf>/_PATH_ACTIVETIMES 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:

name time creator

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 i.e. , a time_t ; see gettimeofday (2). The third field is the electronic mail address of the person who created the group.

HISTORY

Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. R$ This is revision \\$3, dated \\$4. $Id: active.5,v 1.8 1998/08/20 04:24:33 kondou Exp $

SEE ALSO

- ctlinnd (8) - inn conf(5) - innd (8) -

ALIASES(5) UNIX Programmer's Manual ALIASES(5)

N NA AM ME E a al li ia as se es s - aliases file for sendmail

S SY YN NO OP PS SI IS S a al li ia as se es s

D DE ES SC CR RI IP PT TI IO ON N This file describes user ID aliases used by _ /_ u_ s_ r_ /_ s_ b_ i_ n_ /_ s_ e_ n_ d_ m_ a_ i_ l The file resides in _ /_ e_ t_ c and is formatted as a series of lines of the form

name: name_1 name2 name_3

The _ n_ a_ m_ e is the name to alias and the _ n_ a_ m_ e_ __ n are the aliases for that name Lines beginning with white space are continuation lines Lines beginning with `#' are comments

Aliasing occurs only on local names Loops can not occur since no mes- sage will be sent to any person more than once

After aliasing has been done local and valid recipients who have a ``_ _ f_ o_ r_ w_ a_ r_ d'' file in their home directory have messages forwarded to the list of users defined in that file

This is only the raw data file; the actual aliasing information is placed into a binary format in the file _ /_ e_ t_ c_ /_ a_ l_ i_ a_ s_ e_ s_ _ d_ b using the program newaliases(1) A newaliases command should be executed each time the aliases file is changed for the change to take effect

S SE EE E A AL LS SO O newaliases(1) - dbopen (3) - dbm(3) sendmail(8)

_ S_ E_ N_ D_ M_ A_ I_ L _ I_ n_ s_ t_ a_ l_ l_ a_ t_ i_ o_ n _ a_ n_ d _ O_ p_ e_ r_ a_ t_ i_ o_ n _ G_ u_ i_ d_ e

_ S_ E_ N_ D_ M_ A_ I_ L _ A_ n _ I_ n_ t_ e_ r_ n_ e_ t_ w_ o_ r_ k _ M_ a_ i_ l _ R_ o_ u_ t_ e_ r

B BU UG GS S If you have compiled sendmail with DBM support instead of NEWDB you may have encountered problems in dbm(3) restricting a single alias to about 1000 bytes of information You can get longer aliases by ``chaining''; that is make the last name in the alias be a dummy name which is a con- tinuation alias

H HI IS ST TO OR RY Y The a al li ia as se es s file format appeared in 4 0BSD

4th Berkeley Distribution May 19 1998 1

Previous   Next   Man Index

Sections: 0 1 2 3 4 5 6 7 8 N