>>>>> "DW" == Dave Wolfe <dwolfe@risc.sps.mot.com> writes:
DW> The keyword/value idea has a lot of merit, too, and is what I'd like to
DW> see implemented in Mj 2, along with the concept of level or types of
DW> log messages, i.e. informational, warning, error, abort, debugging,
DW> etc.
Don't get too far ahead of me. In Mj2 the debug log is a completely
separate thing and produces gargantuan amounts of stuff. I implemented it
to log in and out of every function called and to produce accurate timing
information. I think it's a rather full-featured debug log, but it isn't
what is needed for generic event logging.
For event logging, Majordomo has very few different kinds of events.
Clients execute commands, so an event is a command. You could log client
"access" calls (once I make the clients actually make access calls during
startup) which would give you a log of every client that starts up, whether
or not they actually did anything. And you could log error conditions.
What else is there?
Note that the routine that sends individual owner notification messages is
driven off of the same call that feeds into the log, and there is a
variable that the owner can set to select what events generate immediate
messages and what events are reported later in a periodic report. (The
reports are what interest me; the log itself isn't something I ever want to
look at.)
- J<
References:
|
|
