innreport doesn't properly track checkpoints across days about inn HOT 3 CLOSED

Comment by iulius on 27 Dec 2008 11:40 UTC
Another solution (suggested by Russ Allbery) is to have some significant changes to how innd logs its article counts, such as resetting the counters each time it logs a checkpoint rather than accumulating the counters until connection close. It used to be, before innfeed when the logging was designed, that no one kept connections open for long periods, but now almost everyone does and that means that one sees very few articles for a long time and then a ton of articles all at once in the statistics when the peer closes the connection for some reason.

from inn.

Comment by iulius on 16 Mar 2010 19:30 UTC
(In [9002]) Change how innd logs its article counts. A checkpoint is added
just before a connection is closed. Checkpoints contain values
accumulated since the last checkpoint.
This way, innreport can rely on checkpoints only, so as to produce
more accurate stats.

see #21

from inn.

Comment by iulius on 19 Mar 2010 19:50 UTC
(In [9016])
Change how innfeed logs its article counts. A checkpoint is added
just before a connection is closed. Checkpoints contain values
accumulated since the last checkpoint.
This way, innreport can rely on checkpoints only, so as to produce
more accurate stats.

See also commit [9002] for innd.

close #21

from inn.