couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-499) allow /etc/default/couchdb to control whether couchdb is started by default
Date Thu, 10 Sep 2009 18:34:57 GMT

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

Paul Joseph Davis commented on COUCHDB-499:
-------------------------------------------

Oh good point. I'm not sure exactly who does use the /etc/default/ system.

I think the couchdb-server idea isn't too bad, but once again, principle of least suprise.
People installing couchdb would probably just default to `apt-get install couchdb` and then
get confused by it not starting. Though, to the same effect, you could instead add a couchdb-core
package that doesn't install the system scripts, and then the couchdb package does. That'd
solve the downstream packagers from the possible trip up.

> allow /etc/default/couchdb to control whether couchdb is started by default
> ---------------------------------------------------------------------------
>
>                 Key: COUCHDB-499
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-499
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 0.10
>         Environment: Ubuntu 9.10 (Karmic)
>            Reporter: Elliot Murphy
>            Priority: Minor
>             Fix For: 0.10
>
>         Attachments: control-service-start.patch
>
>
> couchdb starts by default when installed on Ubuntu (or any debian derivative).
> In Ubuntu, we are including couchdb in the default desktop install.
> however, we are not using the system couchdb, we are starting a per-user couchdb instance
on-demand.
> separately, ubuntu is working on minimizing boot times.
> it would be nice if laptops and netbooks did not have couchdb startup time included in
a normal system boot unless the user really wanted to have the system couchdb starting up.
this is the Ubuntu bug number for reference: https://code.edge.launchpad.net/bugs/427036
> One way to fix this would be to use a variable in /etc/default/couchdb to determine whether
or not to start the system couchdb instance. This is the approach that is taken by pulseaudio,
fetchmail, and monit. I'm discussing this fix with Ubuntu core-devs now: https://code.edge.launchpad.net/~statik/ubuntu/karmic/couchdb/fix-bug427036/+merge/11543
> I'm also attaching a patch which changes the init script and /etc/couchdb/default in
the way I've just described.

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


Mime
View raw message