couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-20) Output from update listener causes error messages/db server crash
Date Fri, 23 Jan 2009 21:18:00 GMT

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

Jan Lehnardt updated COUCHDB-20:
--------------------------------

    Fix Version/s: 1.0

Flag for 1.0. This should be an easy one.

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


Mime
View raw message