From owner-freebsd-questions@FreeBSD.ORG Thu Mar 31 19:44:36 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D78B7106564A for ; Thu, 31 Mar 2011 19:44:36 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from outbound-mail-01.bluehost.com (cpoproxy1-pub.bluehost.com [69.89.21.11]) by mx1.freebsd.org (Postfix) with SMTP id 9F9298FC1C for ; Thu, 31 Mar 2011 19:44:36 +0000 (UTC) Received: (qmail 16109 invoked by uid 0); 31 Mar 2011 19:44:36 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy1.bluehost.com with SMTP; 31 Mar 2011 19:44:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=apotheon.com; h=Date:From:To:Subject:Message-ID:Mail-Followup-To:References:Mime-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent:X-Identified-User; b=logz5H/BS9U0OTGcSLpx6TO9lmMYb9reSgwFMrey1CPdmQ6Vsf534jaisCDb+vXxqkUZdhBi2vffyFf4dVWwy6pla8JKlsxYMJ+8+w0VK+yp6dPQ4Ob95sNlRVFuJUjl; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1Q5NnG-0007zs-PT for freebsd-questions@freebsd.org; Thu, 31 Mar 2011 13:44:35 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Thu, 31 Mar 2011 13:32:17 -0600 Date: Thu, 31 Mar 2011 13:32:17 -0600 From: Chad Perrin To: freebsd-questions@freebsd.org Message-ID: <20110331193217.GA81374@guilt.hydra> Mail-Followup-To: freebsd-questions@freebsd.org References: <4D94A502.2060002@telting.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <4D94A502.2060002@telting.org> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Subject: Re: SSH persistent sessions without screen? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2011 19:44:36 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 31, 2011 at 09:00:02AM -0700, Chris Telting wrote: > I would like to have something like virtual terminals that continue=20 > running no matter if ssh is connected to them or not. Something like=20 > the screen utility. But I don't want to use screen, I'm looking for=20 > something more automated. Maybe even be able to have multiple=20 > connections on different computers. >=20 > I have a number of computers and I like to use each for batch processing= =20 > different stuff, especially compiling. I'm mostly interested in=20 > connecting to running sessions from a mobile android phone. I don't=20 > want to keep having to manually login every time through screen and it=20 > should be tolerant of a dropped connection. >=20 > I'm thinking there is probably a way to do this with just ssh. Maybe=20 > have separate sshd daemons running on specific ports. Any ideas? I'm not 100% clear on what you're trying to avoid from GNU Screen, but my first thought when you said you wanted persistent sessions without GNU Screen was "tmux". Count mine as a third vote for tmux, if that suits your needs. Depending on your actual needs, you could also look into using the nohup command. It's not a terminal multiplexer but, in the words of the manpage, it allows you to "run a command immune to hangups, with output to a non-tty". --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk2U1sEACgkQ9mn/Pj01uKXZpgCeLQ2mLm5OxZcKfNC+FQBb/3b0 JNkAn11voDBGs9DWjbtCwRT6EEk4bvmR =0Boz -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu--