inn 2.4.0 and tdx-util

Kevin Maguire kmaguire at eso.org
Sun Nov 16 13:18:17 UTC 2003


Hi

I am installing (for the first time) inn.  On my system I see
strangeness issues with tdx-util.  Easiest way to explain is with 2
examples:

# tdx-util -i -n comp.lang.tcl
comp.lang.tcl 12 1 1 12 y 0 2016259

# tdx-util -g -n comp.lang.tcl
1 0 269 1068974008 0 @030141000000000000000000794F00000001@
2 269 528 1068974008 0 @0301410000000000000000007AE300000001@
3 797 316 1068974023 0 @0301410000000000000000008D1B00000001@
4 1113 206 1068974069 0 @030141000000000000000000B5A400000001@
5 1319 236 1068974073 0 @030141000000000000000000B6B200000001@
6 1555 319 1068974088 0 @030141000000000000000000C8D400000001@
7 1874 254 1068974113 0 @030141000000000000000000D48900000001@
8 2128 183 1068974120 0 @030141000000000000000000DE5000000001@
9 2311 341 1068974139 0 @030141000000000000000000E9B500000001@
10 2652 376 1068975442 0 @0301410000000000000000017ED900000001@
11 3028 346 1068979502 0 @030141000000000000000001CFBE00000001@
12 3374 401 1068984294 0 @0301410000000000000000023A2C00000001@

If I am not mistaken, that means the documentation is wrong.  The man
page says:

-->
     -g  Dump the master index of the overview database.  This
         contains similar information to the server active file,
         such as high and low water marks and moderation status,
         and is the information that nnrpd hands out to clients.

         The fields are, in order, the newsgroup name, the high
         water mark, the low water mark, the base article number
         (the point at which the group index begins), the count
         of articles in the group, the group status flag, the
         time (in seconds since epoch) when that newsgroup was
         deleted or 0 if it hasn't been, and the inode of the
         index file for that group.

     -i  Dump the index of a particular group.  The fields are,
         in order, the article number, the offset of the data for
         that article in the overview data file for that group,
         the length of the overview data, the time (in seconds
         since epoch) when the article arrived on the server, the
         time (in seconds since epoch) when the article should
         expire based on its Expires header (or 0 if there is no
         Expires header), and the storage API token of the
         article.
-->

but it looks to me if the code does the opposite, and -i and -g
options are reversed in the sense of the fields that are output??

I am using 2.4.0 on Solaris, compiled with gcc.

Am I reading something all wrong here, or .... ?

kevin





More information about the inn-bugs mailing list