From dev-return-7144-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Tue Nov 03 02:44:31 2009 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 51280 invoked from network); 3 Nov 2009 02:44:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Nov 2009 02:44:31 -0000 Received: (qmail 70167 invoked by uid 500); 3 Nov 2009 02:44:30 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 70076 invoked by uid 500); 3 Nov 2009 02:44:30 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 70066 invoked by uid 99); 3 Nov 2009 02:44:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2009 02:44:30 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2009 02:44:20 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5F432234C052 for ; Mon, 2 Nov 2009 18:43:59 -0800 (PST) Message-ID: <443213041.1257216239375.JavaMail.jira@brutus> Date: Tue, 3 Nov 2009 02:43:59 +0000 (UTC) From: "Paul Joseph Davis (JIRA)" To: dev@couchdb.apache.org Subject: [jira] Commented: (COUCHDB-248) The log process should use SASL for logging In-Reply-To: <420734562.1234424639760.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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.