[
https://issues.apache.org/jira/browse/COUCHDB-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725025#action_12725025
]
Paul Joseph Davis commented on COUCHDB-20:
------------------------------------------
I'm thinking we just mark this as invalid. If people don't want to munge their
logs then they should write their update_notifiers to not write to stdout. The
logic to make ports reactive would require a bit of rework.
Ps. I realize its been months since the action, but I'm gonna go through and
start triaging.
Pps. Sorry for ticket spam.
> Output from update listener causes error messages/db server crash
> -----------------------------------------------------------------
>
> Key: COUCHDB-20
> URL: https://issues.apache.org/jira/browse/COUCHDB-20
> Project: CouchDB
> Issue Type: Bug
> Reporter: Noah Slater
> Priority: Minor
> Fix For: 1.0
>
>
> What steps will reproduce the problem?
> 1. Write a program/script that continuously reads its stdin and writes
> something to stdout as stdin line has arrived
> 2. Register it as a db update listener in couch.ini
> [Couch]
> ...
> DbUpdateNotificationProcess=/path/to/daemon
> 3. Start couchdb. Each time db is updated, the listener program receives
> input and writes back to stdout.
> This causes long and obscure error messages in couchdb server concole
> output (not showed here). According to [1], listener is not supposed to
> send anything back.
> It is therefore proposed that whatever is received from the listener is
> merely logged in special log file e. g. notifier_log (which may be
> redirected to /dev/null in couch.ini if not needed).
> [1]
> http://groups.google.com/group/couchdb/browse_thread/thread/a81fb0058ae2430
> b/7285fb233fa10368#7285fb233fa10368
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
