Custom Query (44 matches)
Results (4 - 6 of 44)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#7 | fixed | innreport doesn't properly track checkpoints across days | ||
Description |
When logging incoming article counts, innd logs two types of log messages: closing messages when the remote peer terminates the connection, which summarizes all articles received on that connection and then reset the counter, and checkpoint messages, which say how many articles were received so far. Currently, innreport takes into account checkpoint messages if no subsequent closing message is seen, but since connections can be open for days, this can produce skewed numbers on how many articles have been received. The articles received on previous days aren't properly subtracted from the checkpoint value. One possible solution would be to store a local file holding the last checkpoints that innreport processed, and then read that file at the beginning of a new run and subtract off those numbers from subsequent checkpoints. There would need to be some way to run innreport and not save changes to this file. |
|||
#10 | fixed | Export the same variables from all innshellvars instances | ||
Description |
The different implementations of innshellvars currently use different names for the same variables (SPOOLBASE, for example, in the shell version). We should standardize so that everyone uses the same name for the same thing and everyone exports the same variables. This will break backward compatibility, so needs to be done in a major release. |
|||
#12 | fixed | Add support for Diablo-style hash feeds | ||
Description |
Diablo supports a mechanism to take an incoming feed split across multiple boxes by hashing the message ID and only feeding the articles in a particular hash bucket to a given host. This lets the hosts collectively store a full feed without handling the full traffic on each host. INN should support this sort of hash feed via a flag in newsfeeds. |