INN Changes and Upgrade Information

Table of Contents

  1. Changes from 2.3.4 to 2.3.5
  2. Changes from 2.3.3 to 2.3.4
  3. Changes from 2.3.2 to 2.3.3
  4. Changes from 2.3.1 to 2.3.2
  5. Changes from 2.3.0 to 2.3.1
  6. Upgrading from 2.2 to 2.3
  7. Changes from 2.2 to 2.3
  8. Changes from 2.1 to 2.2

Changes from 2.3.4 to 2.3.5

Changes from 2.3.3 to 2.3.4

Changes from 2.3.2 to 2.3.3

Changes from 2.3.1 to 2.3.2

Changes from 2.3.0 to 2.3.1

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

Changes from 2.1 to 2.2

Last spun 2006-07-19 from POD modified 2005-06-07