Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of dave@muse.net.nz designates
 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGxYWpZxXHPexUzik9MB4R7mU_mhbZnvUkr2hatDqszWo4oYWw@mail.gmail.com>
References: 
 <CAGxYWpbX7raSTRLXEOKLPUTkAqSHD9NN+OUfx77O9CR3nto1hw@mail.gmail.com>
	<CAHZBNKYtVkHh56NUNEW65Jev3SDuSvLCsygfdGSSdrWmym-mog@mail.gmail.com>
	<CAGxYWpZxXHPexUzik9MB4R7mU_mhbZnvUkr2hatDqszWo4oYWw@mail.gmail.com>
Date: Fri, 1 Jun 2012 23:52:50 +0200
Message-ID: 
 <CAHZBNKaE+ZPh_2bgdPQWgcb50+A_92nmkVmzH57xS3DWyvtr+A@mail.gmail.com>
Subject: Re: local.ini settings not taking precedence
From: Dave Cottlehuber <dave@muse.net.nz>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 1 June 2012 22:56, Tim Tisdall <tisdall@gmail.com> wrote:
> I have the same config order as you.

Phew.

> It seems to have written the log level change to local.ini . =A0However, =
I'm
> not sure how to interpret that... =A0does that mean it's giving local.ini=
 the
> highest precedence?

Yes.

> So, I looked at http://localhost:5984/_utils/config.html and it's now
> reporting
> socket_options =A0[{nodelay, true}]
>
> This is after I changed local.ini to have the value
> socket_option =3D [{keepalive, true}, {nodelay, true}]
>
> since both default and local.ini say keepalive is true, it seems odd that
> it's now dropped...

It looks as if local & default inis would merge the proplists, but
it's treated as a simple text replacement when read in local.ini.

Despite fiddling, the only thing I can think of is that maybe you
you've got your sections mis-matched. Can you check this with
curl & confirm?

dave@akai couchdb % curl $COUCH/_config/httpd/socket_options
"[{recbuf, 262144}, {sndbuf, 262144}, {nodelay, true}]"

NB editing the files directly will require restarting couchdb, using
the HTTP API does not.

A+
Dave