Logcheck devel - Oct 2004 - Bug#270018: logcheck specs for hylafax?

I've suggested that logcheck (technically, logcheck-database) include
some material for hylafax, to screen out uninteresting messages in the
logs.  Possibly there might also be some patterns for "interesting"
messages to include as well.  (That is, logcheck already has notions
of what is interesting, but there might be some hylafax specific
things to add that it wouldn't pick up normally.)

After some back and forth, it seems there's some interest in this, but
the logcheck maintainers know nothing of hylafax and I only use it in a
limited setting  (one person, one modem, sending an occasional fax.
no modem pools, no reception, no messaging, not network....)

Could you help us identify log messages for this project?

If you are not familiar with logcheck, it is a tool to search through
logs and alert the administrator to unusual or potential problem
entries.  It has a notion of various kinds of severity of errors, as
well as parnoia of the administrator.  So potentially log items could
fall into different severity levels.

Apparently logcheck does not generally attempt to screen out the
messages generated when a daemon starts or stops, so those are of less
interest.  (It's also more likely I've already got most of them).

Since I have made personal adjustments to my own filters, this is more
in the spirit of community service than solving a personal problem.
(Though some of my filters might be a little broad and miss a real
problem).


Also, apparently, this task is considered primarily a logcheck task,
though I think hylafax could install the necessary patterns on its own
(if it knew them).

The bug on the cc list is the relevant one for this request.

On Sat, 09 Oct 2004, Ross Boylan wrote:

[ snipped abusive non conclusive blabla ]
> ..
if you'd care about that bug, than you should have long ago,
tested the rules that jamie posted aboves 10 days ago!?
he may include those in logcheck-database if they work for you.



--
maks