innreport: INND timer

[Mirek Luc]

On Fri, 2 Feb 2001, Katsuhiro Kondou wrote:

> In article <Pine.GSO.4.30.0101301451170.19682-100000 at boromir>,
> 	Mirek Luc <mirecki at nask.pl> wrote;
>
> } Solaris 8 and inn-CURRENT-20010127. Innreport doesn't recognize log
> } entries like this:
> } <------------------------------------------------------------------------->
> } Unknown entries from news log file:
> } First 42 / 42 lines (100.0%)
> } Jan 29 01:51:48 pippin innd: [ID 702911 news.notice] ME time 3600000 idle 203532
>
> innreport should catch this fortmat, although I've never
> experienced with solaris8.  See line 378 in innreport.
OK. But I found bug/feature/whatever in the innreport_inn.pm module. See
the regexp for "innd timer" (from line 352). This regexp doesn't match the
format of logs in CURRENT. They are different in STABLE and CURRENT:
<----------------------  inn-STABLE  ---------------------------->
Jan 19 01:32:23 pippin innd: [ID 702911 news.warning] ME time 3600140 idle
3128761(106268) artwrite 54735(19396) artlink 0(0) hiswrite 38994(20842)
hissync 244(705) sitesend 20272(13114) artctrl 3846(1295) artcncl
3848(1297) hishave 1161(65939) hisgrep 99(121) perl 246894(19665) overv
27698(19396) python 0(0)
<----------------------  inn-CURRENT  --------------------------->
Feb  2 01:51:53 pippin innd: [ID 702911 news.notice] ME time 3600003 idle
2160594(324071) hishave 3522(186050) hisgrep 745(391) hiswrite
70350(27080) hissync 415(912) artclean 120181(27462) artwrite 68174(26235)
artctrl 6588(1806) artcncl 6640(1809) sitesend 44367(14695) overv
47313(26235) perl 837550(27080)
<---------------------------------------------------------------->
I've just adapted this regexp to _my_ config.

-Mirek