[
https://issues.apache.org/jira/browse/COUCHDB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806295#action_12806295
]
Enda Farrell commented on COUCHDB-412:
--------------------------------------
I favour the approach that allows the 'CustomLog "|/path/to/program" ' - but
as I've not tried to write such a handoff, I don't know if it's difficult or
simply a matter of a config ini setting.
I think it somewhat important that if there's no supervisor process to restart
it, we at least have the ability to call (perhaps the _status?) an API to test
whether or not it is working/running.
> 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.
