Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <50C887E0.10201@yagni.com>
References: 
 <CAGkcVSgzOKh6KRpwwdzads5aad8cbQNCcpJsxbkoDEy-e43O-w@mail.gmail.com>
	<50C887E0.10201@yagni.com>
Date: Wed, 12 Dec 2012 13:59:27 +0000
Message-ID: 
 <CABvT1DFrgVSYW17Uw0pQJT3oeMzEN+VXprsbW_zG0breH9so+g@mail.gmail.com>
Subject: Re: Running couchdb remotely (from an interactive shell)
From: Robert Newson <rnewson@apache.org>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

CouchDB includes a script to launch it as a daemon, a standard init.d
script. I'm confused why you'd ssh to a machine, run couchdb in the
foreground, and log off.


On 12 December 2012 13:34, Wayne Conrad <wconrad@yagni.com> wrote:
> On 12/11/2012 11:53 AM, Nestor Urquiza wrote:
>> As other users have asked in the past to this list couchdb will not
>> run from a remote interactive shell but rather it will be killed when
>> the ssh session terminates. The command nohup can help with that. Here
>> is what I did (which works OK):
>
> Terminal multiplexors like screen and tmux are very good for "I want to
> start a non-daemon, disconnect, and come back later to see what happened."
>
> Here's how it works with screen:
>
> log on
> $ screen
> $ (enter log running command)
> type control-a d to detach the screen session
> log off
>
> later...
>
> log into the remote system
> $ screen -r
>
> and you'll be back in your long running program's term, including any output
> the program printed while you were gone.
>
> Best Regards,
> Wayne Conrad