1INNUPGRADE(8)             InterNetNews Documentation             INNUPGRADE(8)
2
3
4

NAME

6       innupgrade - Upgrade INN configuration files
7

SYNOPSIS

9       innupgrade directory
10
11       innupgrade [-t type] -f file
12

DESCRIPTION

14       innupgrade is intended to be run during a major upgrade of INN to fix
15       the configuration files with any required changes.  If given a
16       directory, it will scan that directory for any files that it has
17       updates defined for, try to perform those updates, and replace the
18       files with updated versions if applying the updates resulted in any
19       changes.  The old versions of the files will be saved with a ".OLD"
20       extension.
21
22       If the -f flag is used, only that file will be updated.  If the file
23       name doesn't match the standard file name of an INN configuration file,
24       the optional -t flag may be given to specify the type.  See "EXAMPLES"
25       for an example of this.
26
27       Currently, innupgrade knows how to apply the following updates:
28
29       inn.conf
30         • Quote values with whitespace and comment out keys with no values,
31           required for the change in configuration parsers introduced in
32           INN 2.4.  The new format is not backward compatible with the
33           previous parser, since the previous parser will include the double-
34           quotes in the value of the parameter.
35
36         • Add the hismethod parameter if not found (introduced in INN 2.4,
37           with the default value "hisv6").  Rename nntpactsync to
38           incominglogfrequency (since INN 2.5).  Rename addnntppostingdate
39           and addnntppostinghost to respectively addinjectiondate and
40           addinjectionpostinghost (since INN 2.6).
41
42         • If the overview.fmt file exists, its content is merged in the
43           extraoverviewadvertised and extraoverviewhidden parameters
44           introduced in INN 2.5.  The file is then renamed to
45           overview.fmt.OLD.
46
47         • If the sasl.conf file exists, its content is merged in the
48           tlscapath, tlscafile, tlscertfile and tlskeyfile parameters
49           introduced in INN 2.5.  The file is then renamed to sasl.conf.OLD.
50
51       newsfeeds
52         • Replace the use of startinnfeed with the appropriate direct
53           invocation of innfeed or imapfeed.
54
55       A few obsolete programs or configuration files are renamed with a
56       ".OLD" extension by innupgrade.  Obsolete man pages are directly
57       removed.
58
59       Normally, innupgrade should be run at least on the pathetc directory
60       after any upgrade of INN other than a patch release (any upgrade that
61       changes the first or second version numbers).  This may occur
62       automatically during the upgrade process.
63

OPTIONS

65       -f file
66           Only act on file rather than working on an entire directory.
67
68       -t type
69           For a file specified with -f, parse it and upgrade it as if it were
70           named type.  Used for upgrading files with the same syntax as
71           normal INN configuration files but with different names.  Only
72           makes sense in combination with -f.
73

EXAMPLES

75       Upgrade any configuration files found in pathetc and append a ".OLD"
76       extension to obsolete files in pathetc:
77
78           innupgrade <pathetc in inn.conf>
79
80       Upgrade only /news/etc/inn.conf:
81
82           innupgrade -f /news/etc/inn.conf
83
84       Upgrade a file named inn-special.conf that should have the same syntax
85       as inn.conf:
86
87           innupgrade -t inn.conf -f inn-special.conf
88
89       Any upgrade rules that apply to inn.conf will be applied to the
90       alternate file.
91

HISTORY

93       Written by Russ Allbery <eagle@eyrie.org> for InterNetNews.
94
95
96
97INN 2.6.5                         2022-01-23                     INNUPGRADE(8)
Impressum