|
|
1.1 root 1: .TH NEWSOUTPUT 8 "University of Illinois"
2: .SH NAME
3: newsoutput, newsinput - notes-news gateway programs
4: .SH SYNOPSIS
5: .B newsoutput
6: [
7: .B "-a"
8: or
9: .BI "-s" sysname
10: or
11: .B "-c"
12: .I "filename"
13: ] [
14: .B "-b"
15: ] [
16: .B "-v"
17: ] [
18: .B "-o"
19: .I date-spec
20: ] [
21: .B "-f"
22: file
23: ]
24: topic [ ... ]
25: .PP
26: .B newsinput
27: .SH DESCRIPTION
28: .I Newsoutput
29: and
30: .I newsinput
31: manage the transfer of articles between a notesfile system
32: and a news system.
33:
34: .I Newsoutput
35: gateways notesfile-generated articles to the news system.
36: Several options determine the types of articles to be
37: transfered.
38: The
39: .B -a
40: option specifies that any notesfile-generated article that
41: has not been in the news system before is to be sent to
42: news.
43: The
44: .BI "-s" "sysname"
45: option specifies that only articles from
46: .I sysname
47: are to be sent to the news system.
48: The
49: .B "-c"
50: option directs
51: .I newsoutput
52: to gateway articles written at any of the systems whose
53: names appear in the file
54: .IB filename "."
55: If none of these options is specified, only locally
56: generated articles are sent to the news.
57: In normal operation, the
58: .B -a
59: or
60: .B -c
61: options are most typically used;
62: .B -s
63: is included for backwards compatibility.
64: .PP
65: The
66: .B -b
67: option specifies that newsoutput should generate articles
68: which will be parsed correctly by previous versions of the
69: notesfile/news gateway code.
70: Files containing lists of notesfiles can
71: be specified through the
72: .B -f
73: option.
74: Use
75: .B -v
76: for a more verbose output than normal;
77: default operation produces a summary of notes and responses
78: transmitted for each notesfile with traffic.
79: .PP
80: The
81: .B -o
82: option specifies that only articles that arrived on the
83: local system after
84: .I date-spec
85: are to be considered for transmittal to news.
86: The timestamp file is updated after the execution of
87: .I newsoutput
88: whether the
89: .B -o
90: option is specified.
91: .PP
92: The actual method of insertion into the news system is determined
93: in the ``net.how'' file by the transmission method for the
94: pseudo-site ``Usenet''.
95: Mappings between notesfiles and newsgroups are specified in the
96: file ``/usr/spool/notes/.utilities/newsgroups''.
97: .PP
98: The
99: .I newsinput
100: program accepts articles from the news system,
101: parses headers,
102: maps newsgroups to appropriate notesfiles,
103: and inserts the articles.
104: News' control messages are intercepted and placed in a
105: maintainence notesfile for review by the system manager.
106: When a news article maps to a non-existent notesfile,
107: the notesfile is automatically created.
108: .PP
109: Typically
110: .I newsoutput
111: is run by cron(8) at intervals ranging from hourly to daily.
112: Newsinput is invoked automatically by the news system when
113: it propogates articles.
114: See appendix B of
115: .ul
116: The Notesfile Reference Manual
117: for a more detailed discussion on configuring and installing
118: a notesfile-news gateway.
119: .PP
120: The notesfile-news mapping function used the file
121: /usr/spool/notes/.utilities to map names between the two systems.
122: The mapping functions allow simple one-for-one name mapping,
123: one-to-many mapping,
124: and
125: mapping ``basenotes'' and responses from one notesfile to
126: separate newsgroups.
127: See appendix B of
128: .ul
129: The Notesfile Reference Manual
130: for more information on how this works.
131: .SH BUGS
132: News articles which can definitely be marked as responses
133: because they have a ``References'' line but whose parents
134: can't be found by article-ID or by guessing from the title
135: are not counted as orphans.
136: This is due to problems arising from mapping of article-ID's
137: to allow a notesfile and news system to coexist on the
138: same host.
139: .PP
140: newsinput doesn't correctly do one-to-many mapping of
141: newsgroups to notesfiles. Newsoutput does do
142: one-to-many mapping of notesfiles to newsgroups.
143: .PP
144: Since the author's system may not have seen the article yet
145: (if he wrote it via nfmail for example), the ``Path:'' header
146: line may not point anywhere near the author.
147: .PP
148: The ``Path'' line generated contains full-domain information
149: and doesn't necessarily point at the author. News systems
150: 2.10.2 and earlier still assume that the last component of
151: this header line is an author name and treat it specially.
152: .SH FILES
153: .PD 0
154: .TP 40
155: /usr/spool/notes/.utilities
156: where these programs live.
157: .TP 40
158: /usr/spool/notes/.utilities/newsgroups
159: mapping between notesfiles and newsgroups
160: .TP 40
161: /usr/spool/notes/.utilities/net.how
162: Pseudo-site ``Usenet'' specifies how to insert news
163: articles.
164: .PD
165: .SH SEE ALSO
166: news(1),
167: notes(1),
168: nfxmit(8),
169: uucp(1),
170: .br
171: .ul
172: The Notesfile Reference Manual
173: .SH AUTHORS
174: .nf
175: Ray Essick (uiucdcs!essick, essick%[email protected])
176: Department of Computer Science
177: University of Illinois at Urbana-Champaign
178: Urbana, IL
179: .sp
180: Rob Kolstad ([email protected])
181: CONVEX Computer Corporation
182: Richardson, TX
183: .fi
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.