[
https://issues.apache.org/jira/browse/COUCHDB-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hammond updated COUCHDB-588:
---------------------------------
Attachment: bug-588.patch
> don't make log noise when an OS process chooses to terminate normally
> ---------------------------------------------------------------------
>
> Key: COUCHDB-588
> URL: https://issues.apache.org/jira/browse/COUCHDB-588
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Mark Hammond
> Assignee: Adam Kocoloski
> Priority: Minor
> Fix For: 0.11
>
> Attachments: bug-588.patch
>
>
> If an "os process" itself chooses to terminate normally (ie, with an exit
> code of zero), couchdb logs a fair bit of noise, including a stack-trace.
> This noise can cause well-meaning users to report a bug when infact the exit
> was expected. This is particularly useful for "externals" - if the
> implementation of the external changes, it can decide to terminate normally
> so the next request causes the new implementation to be picked up.
> The attached patch causes an OS process terminating with a non-zero exit code
> to be treated as before (ie, lots of log information written) while an exit
> code of zero emits a couple of "info" records about the termination with no
> stack-traces etc.
> Assigning to Adam for review - please assign back if it looks OK and I'll
> check it in (and thanks for your pointers - they helped immensely)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.