Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=W2BEd9+BJxmtrtILLu9ecP/mHbJF1t2+FDTvT9lmGBWVSZVzUQFRePZ0F/bRbFubfO
         K2gCBjBkHL+xA2jkM8LNQkH6oV09pypIWSwqYR6/VCpiCXZx78E/T2Du/erMqDfNFqwi
         3K05ILezTnqO5WjwKdpV0VhGrDyNs72+2m+Dk=
MIME-Version: 1.0
In-Reply-To: <4AAA137B-B276-486A-9BEE-C42FAB3F60D2@tumbolia.org>
References: <8294820.59751277478532199.JavaMail.jira@thor>
	<1E86775F-35FB-4CC2-8856-E0C603E36689@tumbolia.org>
	<AANLkTinbOivjofOlDF13UxXrBpcDUuJx7Ob7p-1NVzL9@mail.gmail.com>
	<9DCD1334-2F3E-4985-BD5F-AA0CAFB370AA@tumbolia.org>
	<AANLkTinyPGuthgidIxiNoiU2PbxezcU3f3eMIC9hQROp@mail.gmail.com>
	<AANLkTim7Sgx9vhMKQF_qRmN_V4erZt4NtpmLYefXOcB5@mail.gmail.com>
	<2E5B283E-C10F-4716-A5D1-B312A7F0A04A@tumbolia.org>
	<AANLkTiljdm8yyund1vpiy5GGgB0lLTMQMwhDR1nps7vA@mail.gmail.com>
	<AANLkTilWHpkige3mLF1nlCifYtYl_dOINvShEo49dQn3@mail.gmail.com>
	<4AAA137B-B276-486A-9BEE-C42FAB3F60D2@tumbolia.org>
Date: Fri, 25 Jun 2010 21:13:49 +0200
Message-ID: <AANLkTim25AW2_ol8TyovZJgW4oYDdZXLL4pKqeAxmR8h@mail.gmail.com>
Subject: Re: [jira] Updated: (COUCHDB-393) Cannot discover currently running
	http port if ini file specifies port 0
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jun 25, 2010 at 7:40 PM, Noah Slater <nslater@tumbolia.org> wrote:
> 1.0 should be relatively stable though. So if we're planning to replace the patch with another patch that works differently, is that a good idea. Or do you think both things could live side by side without any trouble?
>

They could live together, but it may be redundant at the end. Is this a problem

If we have some time I could work on another solution. For now I fail
though to find a way to get final port from couch in the shell script.
The only simple way I see for now is to name the CouchDB node and then
call some specific function with erlang that return the correct
information. The list of nodes could be get via erlang too. But do we
want to name the nodes ? (via -sname or such) .

If we don't name the nodes, there may be a way to do it via os pids,
but I don't know it yet.

- benoit