Re: [Sks-devel] A couple of small updates

[Chris Kuethe]

Proposal:

0x0001  general notices, database open,checkpoint,close
0x0002  key error detected

0x0010  membership list at load and reload time
0x0020  high level sync messages, connection to/from & status
0x0040  low lovel sync messages, number of keys recovered
0x0080  insane sync messages, list actual hashes recovered

0x0100  mailsync list at load and reload time
0x0200  high level mailsync messages, "mailing %d keys to %s"
0x0400  low lovel mailsync messages, "sending these hashes:\n%s"
0x0800  insane mailsync messages, the actual mailsync message sent

0x1000  query "/pks/lookup?%s from %s"
0x2000  raw HTTP GET request
Ox4000  key POST summary

Those are the obvious ones i can think of at the moment. rather than
having "ignore error" all over the place, use something like
"log_this(0x0001 'database opened')" and let log_this decide whether
or not the message should be printed.

CK

On Tue, 28 Sep 2004, Yaron Minsky wrote:

> Some kind of more sensible logging system sounds great to me.  And
> logically a set of flags makes more sense than a simple level.  I'd be
> very interested in seeing a proposal/set of patches in that direction.
>
> y
>
> On Tue, 28 Sep 2004 16:57:19 +0200, Dinko Korunic <address@hidden> wrote:
> > On Tue, Sep 28, 2004 at 08:50:25AM -0600, Chris Kuethe wrote:
> > > I'll send a diff once I'm happy with the tuning. Maybe log level should
> > > be a bitmask instead?
> >
> > I would be quite happy with bitmask or any way to specify logs in detail
> > - that way we could easily filter what we want in our logs, possibly
> > rotate them and analyze it in some tool [like Perl+Gnuplot].

--
Chris Kuethe, GCIA CISSP: Secure Systems Specialist - U of A CNS
      office: 157 General Services Bldg.    +1.780.492.8135
              address@hidden

     GDB has a 'break' feature; why doesn't it have 'fix' too?