Tom Feiner wrote: > Thanks for the bug report. As this is a munin issue rather than a debian > issue, this should be handled upstream. I've forwarded this bug to the > upstream bug tracker. > > If you get a chance to write the patch, please include it there, so it can be > incorporated in a future munin release.
I've been looking into this in my spare time. I don't believe it would be a good idea to incorporate this into exim_mailstats. I have found 10 things that exim writes that could be monitored. These items would clutter the current graph and IMO make it unreadable. I took exim_mailstats as a base and made exim_connections. The down side of this is that it parses the exim log 2 times (that is, if one uses both plugins). An exim_log_multi would be better suited for this task. This is the code that gathers the data. I'm not aware of any other connection/disconnection reasons than these. / refused: too many connections from that IP address$/ and $toomany++, next; / connection count / and $connections++, next; / no (?:host name|IP address) found for / and $nordns++, next; / lost(?: |$)/ and $lost++, next; / command timeout / and $timeout++, next; / \(message abandoned\) / and $abandon++, next; / closed after SIG[A-Z]{1,10}$/ and $signal++, next; / unexpected disconnection / and $unexpected++, next; if (/ closed by /) { / DROP in ACL$/ and $dropacl++, next; / QUIT$/ and $quit++, next; } I should point out that with some spam software, the toomany will jump pretty high and could make the other information unreadable on the graph. On one server, I see toomany max at almost 70 where as all the others only top 5. -- Lab tests show that use of micro$oft causes cancer in lab animals Got Gas??? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org