Log rotation (unwanted.log, tally.unwanted)

Bettina Fink laura at hydrophil.de
Sat Jun 23 15:51:37 UTC 2001


on my boxes with older INNs (1.x), the unwanted.log was not
reset every night, the numbers in it accumulated until reset
manually. I liked that behaviour, because usually once a month,
I sat down and read through the unwanted.log looking for useful
hierarchies and groups that got serious traffic.

With the newer INNs, unwanted.log is reset on a daily basis.
I don't find that very useful.

I've never looked too deep into INN's log rotation and analysis,
but it seems that the script that is responsible for the former
behaviour, tally.unwanted, is simply missing in INN 2.x. But
tally.unwanted is still mentioned in scanlogs:

$ grep tally bin/scanlogs

But there is no {PATHBIN}/tally.unwanted:

$ ll bin/tally*
-r-xr-x---   1 news     news         1390 Jun 16 18:56 bin/tally.control*

And it's also not in the source:

$ ll /usr/local/src/inn-STABLE-20010622/scripts/tally*
-rwxr-xr-x    1 news     local        1380 Jun 22 17:11 /usr/local/src/inn-STABLE-20010622/scripts/tally.control*
-rw-r--r--    1 news     local        1421 Nov 15  1999 /usr/local/src/inn-STABLE-20010622/scripts/tally.control.in

Bug or feature?


More information about the inn-workers mailing list