Warren Togami created COUCHDB-2264:
--------------------------------------
Summary: stdout should not print database activity
Key: COUCHDB-2264
URL: https://issues.apache.org/jira/browse/COUCHDB-2264
Project: CouchDB
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Warren Togami
https://github.com/apache/couchdb/blob/master/etc/init/couchdb.tpl.in
http://pkgs.fedoraproject.org/cgit/couchdb.git/tree/couchdb.init?h=f20
Old sysv init scripts ran couchdb with the -b option which used -o and -e to
redirect stdout and stderr elsewhere. The default /var/log/couchdb/couch.log
sees only this at startup:
[Thu, 03 Jul 2014 05:47:53 GMT] [info] [<0.32.0>] Apache CouchDB has started on
http://127.0.0.1:5984/
http://pkgs.fedoraproject.org/cgit/couchdb.git/tree/couchdb.service?h=f20
Here is an example of a systemd .service file for couchdb. Since it does not
use -o and -e, all stdout and stderr messages are logged in journal/syslog.
This is redundant as all the database activity is already logged to
/var/log/couchdb/couch.log.
Adding -o /dev/null -e /dev/null to the systemd .service would suffice in
silencing the redundant logging. However it also stops printing helpful
messages like:
Apache CouchDB 1.6.0 (LogLevel=info) is starting.
Apache CouchDB has started. Time to relax.
[info] [<0.32.0>] Apache CouchDB has started on http://127.0.0.1:5984/
I humbly request the following...
* If couchdb is logging the database activity refrain from redundantly printing
to stdout. Provide an option to bring it back for people that want the old
behavior.
* With stdout far less noisy, services no longer need to silence it. You can
print additional useful messages during startup, perhaps something like:
Apache CouchDB 1.6.0 (LogLevel=info) is starting.
Apache CouchDB logging to /var/log/couchdb/couch.log
Apache CouchDB has started. Time to relax.
[info] [<0.32.0>] Apache CouchDB has started on http://127.0.0.1:5984/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
