couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Hooker (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-412) CouchDB fails to start when log file is a pipe
Date Wed, 20 Jan 2010 08:56:01 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matthew Hooker updated COUCHDB-412:
-----------------------------------

    Attachment: pipe_wrapper.sh
                COUCHDB_412_01.patch

This is a "rough draft" of a potential fix for this issue. 

This patch makes it so all writes to the log file happen through a port to the attached wrapper
script. 

If people think this is a good approach the problem, a few more things should be done:

1. only use the pipe wrapper if the target file is a named pipe, otherwise use standard file
descriptors.
2. find win32 solution (if applicable)

I think a risk with this approach is if the wrapper script is aborted for some reason. There's
no supervisor process to restart it, so logs will stop working.

> 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.


Mime
View raw message