Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <165223418.1252428237889.JavaMail.jira@brutus>
Date: Tue, 8 Sep 2009 09:43:57 -0700 (PDT)
From: "Noah Slater (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-498) .ini file chaining not properly
 reset by -n switch
In-Reply-To: <1368741154.1252426558129.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752599#action_12752599 ] 

Noah Slater commented on COUCHDB-498:
-------------------------------------

My last comment was so hilariously wrong, I just deleted it. Pretend I said nothing.

> .ini file chaining not properly reset by -n switch
> --------------------------------------------------
>
>                 Key: COUCHDB-498
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-498
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.10
>         Environment: Ubuntu Linux 09.10 (karmic) unreleased
>            Reporter: eric casteleijn
>             Fix For: 0.10
>
>
> I've added as line 220 in /usr/bin/couchdb:
>     echo "startarguments: $start_arguments"
> Now, when I do:
> /usr/bin/couchdb -n -a /tmp/tmp871WkT/xdg_config/desktop-couch/desktop-couchdb.ini -p /tmp/tmp871WkT/xdg_cache/desktop-couch/desktop-couchdb.pid -o /tmp/tmp871WkT/xdg_cache/desktop-couch/desktop-couchdb.stdout -e /tmp/tmp871WkT/xdg_cache/desktop-couch/desktop-couchdb.stderr -b
> I get:
> Apache CouchDB has started, time to relax.
> eric@thelog:~$ startarguments:  \"/etc/couchdb/default.ini\", \"/etc/couchdb/local.ini\",  \""/etc/couchdb/default.ini"\", \""/tmp/tmp871WkT/xdg_config/desktop-couch/desktop-couchdb.ini"\"
> which suggests to me that the -n switch in this case does not actually reset the .ini chain.
> This came to light when I noticed that any admin users I added in my system CouchDB also affected any other CouchDB I ran on the same machine. Which seems logical if my analysis of the bug is correct, since the admin users would be stored in /etc/couchdb/local.ini which is always picked up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.