Yeah, I understand these reservations. I also learned that systemd
handles stdout/stderr logging on its own now, so if that's the
default on the bulk of popular UNIXes, perhaps this is a retrograde
choice.
That said it is the *only* choice I can support on Windows, where
there is no system-wide
It's not proposed to log to /var/log, but ./var/log. Big difference :)
I'll respond to the other point separately.
- Original Message -
From: "Robert Samuel Newson"
To: dev@couchdb.apache.org
Sent: Tuesday, August 2, 2016 4:30:12 PM
Subject: Re: [PROPOSAL] CouchDB
oh, as for /var/log/, that'd be a violation of LSB policy, right? That's not
our place to play unless invited.
> On 2 Aug 2016, at 21:29, Robert Samuel Newson wrote:
>
> My concern is that (and we've seen this with BigCouch), folks won't configure
> log rotation until
My concern is that (and we've seen this with BigCouch), folks won't configure
log rotation until they have either a whopping great log file or, more
typically, been woken by a paging system as their filesystem hit 100%.
Given this method of logging also forces a copytruncate approach to
Seems reasonable to me. I wonder if we should add a stdout log line that
indicates where logs are going? Would be easy to add that as a module callback
so it would work for stderr, file, and syslog.
> On Aug 2, 2016, at 2:36 PM, Joan Touzet wrote:
>
> Presently, CouchDB
Presently, CouchDB 2.0 logs only to stderr. I have opened a PR
to switch this behaviour to log to the ./var/log/couchdb.log
release-local file by default:
https://github.com/apache/couchdb/pull/435
This behaviour is easily overridden in the default.ini/local.ini
files if desired.
I'm not sure