Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <1128854094.367871263989814468.JavaMail.jira@brutus.apache.org>
Date: Wed, 20 Jan 2010 12:16:54 +0000 (UTC)
From: "Brian Candler (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-412) CouchDB fails to start when log
 file is a pipe
In-Reply-To: <2135790957.1247489475628.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802805#action_12802805 ] 

Brian Candler commented on COUCHDB-412:
---------------------------------------

I think this should be made a general facility to log via an external program: i.e. don't hardcoded the path to pipe_wrapper.sh, or the fact that it requires a filename argument for the log destination.

This would then be comparable to the corresponding feature in Apache httpd:

CustomLog "|/path/to/program" ...

It would let you do lots of cool things: e.g. log to syslog or log via HTTP to another couchdb server, without having to launch another process which tails a pipe.


> CouchDB fails to start when log file is a pipe
> ----------------------------------------------
>
>                 Key: COUCHDB-412
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-412
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.9
>         Environment: CentOS x86_64
>            Reporter: Enda Farrell
>         Attachments: COUCHDB_412_01.patch, pipe_wrapper.sh
>
>
> I have an 0.9 CouchDB. When the local.ini file's [log] file is actually a pipe (with a known to be running consumer) rather than a file, CouchDB fails to start.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.