Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#4 Flush outstanding throttled messages at EOF

open
nobody
None
5
2003-05-30
2003-05-30
Anonymous
No

When invoked with --examine-file it would be very
useful if swatch could examine any throttled messages
which have yet to have their timer exceeeded when the
file's EOF is reached, and for each one print out a
report of the form 'xx in
<Time_of_last_log_matching_message -
time_from_throttle-start> matching <throttle-expression>

In the current setup if 300 messages were to appear
meeting a throttled rule only the first will be
reported unless a 301st message meeting that rule is
encountered some time after the throttle timeout. This
can never happen if you first hit EOF when reading the
file. This results in only a single line being
reported in the final log summary with no way of
indicating that 300 were actually encountered.

Thanks,

Martin (mjones@eso.org)

Discussion