lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: couchdb (Ubuntu Lucid)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Debian fixed this in 1.1.0-2. This version likely will not make it in to
Precise as-is; someone needs to go through SRU procedure. I am closing
the bugtasks for old versions of Ubuntu and adding ones for new versions
** Changed in: couchdb (Ubuntu Karmic)
Status: Triaged => Invalid
--
You
** Changed in: couchdb (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/448682
Title:
Cannot stop couchdb using /etc/init.d/couchdb after package install
To
** Changed in: couchdb (Debian)
Status: Unknown => New
--
Cannot stop couchdb using /etc/init.d/couchdb after package install
https://bugs.launchpad.net/bugs/448682
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Some conversations with cjwatson on IRC lead to two potential fixes to
address the issue:
1. < cjwatson> mathiaz: I meant calling sigaction in the daemon itself
2. < cjwatson> or create a tiny C wrapper that does struct sigaction sa;
memset (&sa, 0, sizeof sa); sa.sa_handler =
couchdb will not be killed by its init script because signal 1 is
ignored if the daemon has been started during package installation:
$ cat /proc/$(cat /var/run/couchdb/couchdb.pid)/status
[...]
SigIgn: 1007
[...]
If couchdb has been started by its init script during boot time or from
