Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <CAJ_m3YAmXj1kYAG-egEWEbAs5r5d9T9RajHFsiNb1MmRD1zoZg@mail.gmail.com>
References: <1616023657.515.1470166657892.JavaMail.Joan@Brain>
 <926DF775-71CB-4DA3-A14F-C5AECC7EA1ED@gmail.com> <E911553E-E2E1-4D8F-85F2-7FD6C3F10252@apache.org>
 <820205773.517.1470170303333.JavaMail.Joan@Brain> <CAJ_m3YCPS9im5Tc8Ea=ph1Xx-e5rxn48Qe0bEzGzVb+D_j5xsw@mail.gmail.com>
 <1470732742.2570386.690028481.71307F39@webmail.messagingengine.com>
 <31135394.279.1470768325982.JavaMail.Joan@RITA> <5FCE94B6-81A2-4349-BE10-5C980E30F219@jan.io>
 <CAHdjipJoh9-1HChMa5n1DeMPnz7JHYgh5N1ZaEyopObAoM7TJg@mail.gmail.com>
 <CAJ_m3YC8qQE49V+jttepgfx6HDqQB8yR4EHzRnX3NeBjTOES2A@mail.gmail.com> <CAJ_m3YAmXj1kYAG-egEWEbAs5r5d9T9RajHFsiNb1MmRD1zoZg@mail.gmail.com>
From: Alexander Shorin <kxepal@gmail.com>
Date: Wed, 10 Aug 2016 00:28:18 +0300
Message-ID: <CAHdjipJDcTahVcbLnsuOBH6HbR_P7neJWm76Vzw1wtBz7Qf72Q@mail.gmail.com>
Subject: Re: [PROPOSAL] CouchDB 2.0 log to ./var/log/couchdb.log by default
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Tue, 09 Aug 2016 21:28:24 -0000

I actually not sure what happens in stdout and do we really need that.
Good size of stderr is that it's the only source that can reveal
startup crashes, before couch_log will be initialized to write
anything to file.
--
,,,^..^,,,


On Wed, Aug 10, 2016 at 12:22 AM, Paul Davis
<paul.joseph.davis@gmail.com> wrote:
> Meh. Just create a stdout module that proxies calls to stderr (or vice
> versa) and then just make a config thing at the top. Should be as
> simple as I first thought that way.
>
> On Tue, Aug 9, 2016 at 4:22 PM, Paul Davis <paul.joseph.davis@gmail.com> wrote:
>> New logging also doesn't actually have stdout as an option but that'd
>> be a trivial change to make. Though the name of the writer could be
>> weird.
>>
>> On Tue, Aug 9, 2016 at 4:06 PM, Alexander Shorin <kxepal@gmail.com> wrote:
>>> On Tue, Aug 9, 2016 at 10:00 PM, Jan Lehnardt <mail@jan.io> wrote:
>>>> I'd say we keep 1.x behaviour of logging to file by default with an option to override to stdX for the envs that want that.
>>>
>>> Actually, 1.x behaviour is about to log both to stdout/stderr and file
>>> at the same time. Package maintainers actually just suppress
>>> stdout/stderr because we already have a file logging. Those options -o
>>> and -e about to redirect stdout/stderr to specific files, but this
>>> doesn't overrides file logging.
>>>
>>> --
>>> ,,,^..^,,,