1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
|
Changes from 2.3.1 to 2.3.2
* innxmit can again handle regular filenames as input as well as storage
API tokens (allowing it to be used to import an old traditional
spool).
* Several problems with tagged-hash history files have been fixed thanks
to the debugging efforts of Andrew Gierth and Sang-yong Suh.
* A very long-standing (since INN 1.0!) NNTP protocol bug in nnrpd was
fixed. The response to an ARTICLE command retrieving a message by
message ID should have the message ID as the third word of the
response, not the fourth. Fixing this is reported to *possibly* cause
problems with some Netscape browsers, but other news servers correctly
follow the protocol.
* Some serious performance problems with expiration of tradspool should
now be at least somewhat alleviated. tradspool and timehash now know
how to output file names for removal rather than tokens, and fastrm's
ability to remove regular files has been restored. This should bring
expiration times for tradspool back to within a factor of two of
pre-storage-API expiration times.
* An item that was actually changed in 2.3.0 but wasn't noted in NEWS
when it should have been: Users can no longer post articles
containing Approved: headers to moderated groups by default; they must
be specifically given that permission with the access: parameter in
readers.conf. See the man page for more details.
* Added a sample subscriptions file and documentation for it and
innmail.
Changes from 2.3.0 to 2.3.1
* inews no longer downloads the active file, no longer tries to send
postings to moderated groups to the moderator directly, and in general
duplicates less of the functionality of nnrpd, instead letting nnrpd
handle it. This fixes the problem of inews not working properly for
users other than news without being setgid.
* Added a man page for ckpasswd.
* A serious bug in the embedded Perl authentication hooks was fixed,
thanks to Jan Rychter.
* The annoying compilation problem with embedded Perl filtering on Linux
systems without libgdbm installed should be fixed.
* INN now complaints loudly at configure time if the configured path for
temporary files is world-writeable, since this configuration can be a
security hole.
* Many other varied bug fixes and documentation fixes of all sorts.
Upgrading from 2.2 to 2.3
Simply doing a make update is not sufficient to upgrade; the history and
overview information will also have to be regenerated, since the formats
of both files have changed between 2.2 and 2.3. Regardless of whether
you were using the storage API or traditional spool under 2.2, you'll
need to rebuild your overview and history files.
If you want to allow readers, or if you want to expire based on
newsgroup name, you need to tell INN to generate overview data and pick
an overview method by setting ovmethod in inn.conf. See INSTALL and
inn.conf(5) for more details.
The code that generates the dbz index files has been split into a
seperate program, makedbz. makehistory still generates the base history
file and the overview information, but some of its options have been
changed. To rebuild the history and overview files, use:
makehistory -b -f history.n -O -T/usr/local/news/tmp -l 600000
(Change the /usr/local/news/tmp path to some directory that has plenty
of temporary space, and leave off -O if you're running a transit-only
server and don't intend to expire based on group name, and therefore
don't need overview.) Or use:
makehistory -b -f history.n -O -F
(This is suitable for ``buffindexed'' ovmethod.) Both will generate a
new history file as history.n and rebuild overview at the same time. If
you want to preseve a record of expired message IDs in the history file,
run:
awk 'NF==2 { print; }' < history >> history.n
to append them to the newly created history file. Look over the new
history file and make sure it looks right, then generate the new index
files and move them into place:
makedbz -s `wc -l <history.n` -f history.n
mv history.n history
mv history.n.dir history.dir
mv history.n.hash history.hash
mv history.n.index history.index
(Rather than .hash and .index files, you may have a .pag file if you're
using tagged hash.)
For a reader machine, nnrp.access has been replaced by readers.conf.
There currently isn't a program to convert between the old format and
the new format (if you'd like to contribute one, it would be welcomed
gratefully). The new file is unfortunately considerably more complex to
support its new capabilities; please carefully read the example
readers.conf provided and the man page when setting up your initial
configuration. The provided commented-out examples cover the most
common installation (IP-based authentication for all machines on the
local network).
INN makes extensive use of mmap for the new overview mechanisms, so at
the present time NFS-mounting the spool and overview from one central
server on multiple reader machines probably isn't feasible in this
version. mmap tends to interact poorly with NFS (at the least, NFS
clients won't see updates to the mapped files in situations where they
should). (The preferred way to fix this would, rather than backing out
the use of mmap or making it optional, to add support for Diablo-style
header feeds and pull-on-demand of articles from a master server.)
The flags for overchan have changed, plus you probably don't want to run
overchan at all any more. Letting innd write overview data itself
results in somewhat slower performance, but is more reliable and has a
better failure mode under high loads. Writing overview data directly is
the default, so in a normal upgrade from 2.2 to 2.3 you'll want to
comment out or remove your overchan entry in newsfeeds and set
useoverchan to false in inn.conf.
crosspost is no longer installed, and no longer works (even with
traditional spool). If you have an entry for crosspost in newsfeeds,
remove it.
If you're importing a traditional spool from a pre-storage API INN
server, it's strongly recommended that you use NNTP to feed the articles
to your new server rather than trying to build overview and history
directly from the old spool. It's more reliable and ensures that
everything gets put into the right place. The easiest way to do this is
to generate, on your old server, a list of all of your existing article
files and then feed that list to innxmit.
If you are using a version of Cleanfeed that still has a line in it
like:
$lines = $hdr{'__BODY__'} =~ tr/\n/\n/;
you will need to change this line to:
$lines = $hdr{'__LINES__'};
to work with INN 2.3 or later. This is due to an internal optimization
of the interface to embedded filters that's new in INN 2.3.
Changes from 2.2 to 2.3
* New readers.conf file (replaces nnrp.access) which allows more
flexible specification of access restrictions. Included in the sample
implementations is a RADIUS-based authenticator.
* Unified overview has been replaced with an overview API, and there are
now three separate overview implementations to choose from. One
(tradindexed) is very like traditional overview but uses an additional
index file. The second (buffindexed) uses large buffers rather than
separate files for each group and can handle a higher incoming article
rate while still being fast for readers. The third (ovdb) uses
Berkeley DB to store overview information (so you need to have
Berkeley DB installed to use it). The ovmethod key in inn.conf
chooses the overview method to use.
Note that ovdb has not been as widely tested as the other overview
mechanisms and should be considered experimental.
* All article storage and retrieval is now done via the storage API.
Traditional spool is now available as a storage type under the storage
API. (Note that the current traditional spool implementation causes
nightly expire to be extremely slow for a large number of articles, so
it's not recommended that you use the tradspool storage method for the
majority of a large spool.)
* The timecaf storage method has been added, similar to timehash but
storing multiple articles in a single file. See INSTALL for details
on it.
* INN now supports embedded Python filters as well as Perl and TCL
filters, and supports Python authentication hooks.
* There is preliminary support for news reading over SSL, using OpenSSL.
* Users can no longer post articles containing Approved: headers to
moderated groups by default; they must be specifically given that
permission with the access: parameter in readers.conf. See the man
page for more details.
* To simplify anti-abuse filtering, and to be more compliant with news
standards and proposed standards, INN now treats as control messages
only articles containing a Control header. A Subject line beginning
with "cmsg " is no longer sufficient for a message to be considered a
control message, and the Also-Control header is no longer supported.
* inews is not installed setgid news and rnews is not installed setuid
root by default any more. If you need the old permissions, you have
to give a flag to configure. See INSTALL for more details.
* The INN build system no longer uses subst. (This will be transparent
to most users; it's an improvement and modernization of how INN is
configured.)
* The build and installation system has been substantially overhauled.
make update now updates scripts as well as binaries and documentation,
there is better support for parallel builds (with make -j), there is
less needless make recursion, and far more of the system-dependent
configuration is handled directly by autoconf. libtool build support
(including shared library support) should be better than previous
releases.
* All of the applicable bug fixes from INN 2.2.1 and 2.2.2 are also
included in INN 2.3.
Changes from 2.1 to 2.2
* New storage.conf file (replaces storage.ctl).
* New (optional) way of handling non-cancel control messages
(controlchan) that serializes them and prevents server overload from
control message storms.
* Support for actsyncd to fetch active file with ftp; configured by
default to use <ftp://ftp.isc.org/pub/usenet/CONFIG/active.Z> if you
run actsyncd. Be sure to read the manual page for actsync to
configure an actsync.ign file for your site, and test simpleftp if you
do not configure with wget or ncftp. Also see
<ftp://ftp.isc.org/pub/usenet/CONFIG/README>.
* Some options to configure are now moved to inn.conf (merge-to-groups
and pgp-verify).
* inndf, a portable version of df(1) is supplied.
* New cnfsstat program to show stats of cnfs buffers.
* news2mail and mailpost programs for gatewaying news to mail and mail
to news are supplied.
* pullnews program for doing a sucking feed is provided (not meant for
large feeds).
* The innshellvars.csh.in script is obsolete (and lives in the obsolete
directory, for now).
|
