[
https://issues.apache.org/jira/browse/COUCHDB-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772845#action_12772845
]
Paul Joseph Davis commented on COUCHDB-248:
-------------------------------------------
@Adam,
Sadly, I don't know whats normal either. :) I guess maybe I was assuming that
there'd be a log4j style logging system that we should be plugging into. Though
I have seen other loggers (RabbitMQ I think?) that looked like they were using
a system log thinger. Though I definitely see your point on those being
entirely too verbose for access logs.
@Din,
If you're still interested in taking a crack at this, I think the first step
would be to check out current projects and see what they do for logging. I
would suggest looking at Yaws, RabbitMQ, ejabberd to see if you can figure out
if they're using a system logger similarly to ours or doing something that
appears to be more built-in. If it turns out that our system isn't as
non-standard as I had originally thought then this might not actually be much
of a patch.
There are plenty of other tickets that could be worked on if you're still
interested in writing patches. If you want I can go through and find a couple
candidates that would be of similar effort to get you started. We're always
looking for fresh eyes and new ideas.
> The log process should use SASL for logging
> -------------------------------------------
>
> Key: COUCHDB-248
> URL: https://issues.apache.org/jira/browse/COUCHDB-248
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Affects Versions: 0.9
> Environment: any
> Reporter: Ulises Cervino Beresi
> Priority: Minor
>
> As it stands the log process is ad-hoc since it was written from scratch.
> Making it a wrapper around SASL (http://erlang.org/doc/apps/sasl/index.html)
> would be a good improvement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
