[
https://issues.apache.org/jira/browse/COUCHDB-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754492#action_12754492
]
Brian Candler commented on COUCHDB-499:
---------------------------------------
On my Ubuntu Hardy desktop:
$ ls /etc/default/
acpid ddclient pcmcia
acpi-support devpts pmi
alsa exim4 portmap
apache2 fetchmail pound
apache2.dpkg-old hal powernowd
apmd halt pulseaudio
apport iodine rcS
avahi-daemon klogd rsync
bittorrent linux-restricted-modules-common slapd
bluetooth lvm-common smartmontools
bluetooth.dpkg-new mdadm ssh
bootlogd nfs-common syslogd
brltty nfs-kernel-server tmpfs
console-setup ntp ufw
cupsys ntpdate useradd
dbus nvidia-kernel
In most cases these files aren't used for deciding whether the server is
stopped or started. e.g.
$ cat /etc/default/ntp
NTPD_OPTS='-g'
$
If you want that package installed but not running, you'd use update-rc.d
However perhaps a better example is exim4, which has a number of options
including no daemon, or a daemon which is just a queue runner, or a daemon
which is both queue runner or smtp listener. This is configured in
/etc/default/exim4 and so the user can select it using dpkg-reconfigure
# /etc/default/exim4
EX4DEF_VERSION=''
# 'combined' - one daemon running queue and listening on SMTP port
# 'no' - no daemon running the queue
# 'separate' - two separate daemons
# 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from
# /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# options for daemon listening on port 25
SMTPLISTENEROPTIONS=''
Regards,
Brian.
> 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.
