1PRUNEHISTORY(8) System Manager's Manual PRUNEHISTORY(8)
2
6 prunehistory - remove tokens from Usenet history file
7
9 prunehistory [ -f filename ] [ -p ]
10
12 Prunehistory modifies a history(5)-format text file to ``remove'' a set
13 of tokens from it. The tokens are removed by overwriting them with
14 spaces, so that the size and position of any following entries does not
15 change. This has an effect similar to expiring the article, in that it
16 is still mentioned in the history database but cannot be retrieved.
17 Prunehistory reads the standard input. The input is taken as a set of
19 lines. Blank lines and lines starting with a number sign (``#'') are
20 ignored. All other lines are should consist of a Message-ID followed
21 by zero or more other fields (which are ignored).
22 The Message-ID is used as the dbz(3) key to get an offset into the text
24 file.
25 Since innd(8) only appends to the text file, prunehistory does not need
27 to have any interaction with it.
28
30 -p Prunehistory will normally complain about lines that do not fol‐
31 low the correct format. If the ``-p'' flag is used, then the
32 program will silently print any invalid lines on its standard
33 output. (Blank lines and comment lines are also passed
34 through.) This can be useful when prunehistory is used as a
35 filter for other programs such as reap.
36 -f filename
38 The default name of the history file is
39 <pathdb in inn.conf>/history; to specify a different name, use
40 the ``-f'' flag.
41
43 Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is
44 revision 5909, dated 2002-12-03.
45
47 dbz(3), history(5), inn.conf(5), innd(8).
48 PRUNEHISTORY(8)