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.
On Wed, Nov 11, 2009 at 12:07 PM, Mikhail A. Pokidko
<[email protected]> wrote:
> On Wed, Nov 11, 2009 at 1:54 PM, Robert Campbell <[email protected]> wrote:
>> Here is me running "couchdb -b" three times w/ps -A | grep couchdb:
>>
>> r...@default:~# couchdb -b
>> Apache CouchDB has started, time to relax.
>> r...@default:~# couchdb -b
>> Apache CouchDB has started, time to relax.
>
> _-d_ is the clue.
>
> After successful start-up you should try to stop couchdb manually
> with -d option.
>
>
> --
> xmpp: pma AT altlinux DOT org
>
