On 19 Dec 2009, at 23:11, Paul Davis wrote: > On Sat, Dec 19, 2009 at 6:08 PM, viatropos <[email protected]> wrote: >> >> There are a few things that might have caused the problem I'm thinking: >> >> 1) Calling "couchdb &" multiple times? I'm not sure what's best practice >> for starting and knowing you've started couchdb... > > Yeah, don't do that. When you start couchdb use 'couchdb -b` and > `couchdb -k` to start and stop a background process.
Or use the init.d script, and hook it into your runlevels so that it is started on boot. The README has more instructions for you.
