couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes J. Schmidt (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-2246) Make OS daemons configuration key available
Date Tue, 20 May 2014 13:30:39 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Johannes J. Schmidt updated COUCHDB-2246:
-----------------------------------------

    Description: 
When registering an os_daemon

{code}
[os_daemons]
my_daemon = /usr/bin/command
{code}

there is no possibility to access the key *my_daemon*.

I would like to manage daemon configuration under the specific key, which enables having different
configurations for multiple instances of a single daemon script:

{code}
[os_daemons]
slow_daemon = /usr/bin/command
fast_daemon = /usr/bin/command

; settings for instance slow_daemon of /usr/bin/command
[slow_daemon]
dbs: _users,_replicator
speed: 1

; settings for instance fast_daemon of /usr/bin/command
[fast_daemon]
dbs: projects,clients
speed: 10
{code}

I think this could be done via a new command, eg
{code}
["key"]\n
{code}
which would return:
{code}
"fast_daemon"\n
{code}

Alternatively CouchDB could set an environment variable, eg COUCHDB_DAEMON_CONFIG_KEY.

Both method should not break backwards compatibility.

  was:
When registering an os_daemon

{code}
[os_daemons]
my_daemon = /usr/bin/command
{code}

there is no possibility to access the key *my_daemon*.

I would like to manage daemon configuration under the specific key, which enables having different
configurations for multiple instances of a single daemon script:

{code}
[os_daemons]
slow_daemon = /usr/bin/command
fast_daemon = /usr/bin/command

; settings for instance slow_daemon of /usr/bin/command
[slow_daemon]
dbs: _users,_replicator
speed: 1

; settings for instance fast_daemon of /usr/bin/command
[fast_daemon]
dbs: projects,clients
speed: 10
{code}

I think this could be done either via a new command, eg
{code}
["key"]\n
{code}
or via environment variable, without breaking backwards compatibility.


> Make OS daemons configuration key available
> -------------------------------------------
>
>                 Key: COUCHDB-2246
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2246
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>            Reporter: Johannes J. Schmidt
>
> When registering an os_daemon
> {code}
> [os_daemons]
> my_daemon = /usr/bin/command
> {code}
> there is no possibility to access the key *my_daemon*.
> I would like to manage daemon configuration under the specific key, which enables having
different configurations for multiple instances of a single daemon script:
> {code}
> [os_daemons]
> slow_daemon = /usr/bin/command
> fast_daemon = /usr/bin/command
> ; settings for instance slow_daemon of /usr/bin/command
> [slow_daemon]
> dbs: _users,_replicator
> speed: 1
> ; settings for instance fast_daemon of /usr/bin/command
> [fast_daemon]
> dbs: projects,clients
> speed: 10
> {code}
> I think this could be done via a new command, eg
> {code}
> ["key"]\n
> {code}
> which would return:
> {code}
> "fast_daemon"\n
> {code}
> Alternatively CouchDB could set an environment variable, eg COUCHDB_DAEMON_CONFIG_KEY.
> Both method should not break backwards compatibility.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message