[
https://issues.apache.org/jira/browse/COUCHDB-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliot Murphy updated COUCHDB-499:
----------------------------------
Attachment: control-service-start.patch
> 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.
