@Mikhail - but when I tried to specify the PID file I found in /var/run, it didn't work:
r...@default:~# couchdb -b -p /var/run/couchdb Apache CouchDB needs a regular PID file: /var/run/couchdb I just want the init.d scripts to work as they're supposed to. Is there some special trick you have to perform after "apt-get install couchdb"? I can't imagine I'm the only one whose init.d/couchdb won't stop the DB in two completely different Ubuntu & CouchDB versions and installations. On Wed, Nov 11, 2009 at 12:57 PM, Mikhail A. Pokidko <[email protected]> wrote: > On Wed, Nov 11, 2009 at 2:54 PM, Robert Campbell <[email protected]> wrote: >> Sorry, I screwed that up. I saw the d as b for some reason. Here's the >> results from -d: >> >> r...@default:~# ps -A | grep couchdb >> 4389 ? 00:00:00 couchdb >> 4419 ? 00:00:00 couchdb >> 6399 ? 00:00:05 couchdb >> r...@default:~# couchdb -d >> r...@default:~# ps -A | grep couchdb >> 4389 ? 00:00:00 couchdb >> 4419 ? 00:00:00 couchdb >> 6399 ? 00:00:05 couchdb >> r...@default:~# curl -X GET localhost:5984 >> {"couchdb":"Welcome","version":"0.10.0"} >> r...@default:~# >> >> So basically it doesn't seem to do anything. The processes are still >> running and the couchdb server is still responding to requests. > > That`s why i prefer to indicate pid explicitly) You can be sure that > you operate with instance you exactly need. > > > > > -- > xmpp: pma AT altlinux DOT org >
