From owner-freebsd-questions@FreeBSD.ORG Wed May 13 08:27:08 2009 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 48200106566B for ; Wed, 13 May 2009 08:27:08 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id C80E18FC0C for ; Wed, 13 May 2009 08:27:06 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by ey-out-2122.google.com with SMTP id 9so175141eyd.7 for ; Wed, 13 May 2009 01:27:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=eDuAEGN27CfZK3OfsMipCUodiIPT+CKajVhMnz5RDOw=; b=P8B5H1UPzOXTWr/bsXwW34YeKVlki4K7nUOKX+7/6I6Q44SiS+yhgAlZsrJpJlTtHE 2nPwoxpTxgx1vHB2uYO1499PGNi03rOI727rWFsF44K8liBdiUGV1f5ztBNQbV7xHwsB W9LbGz+B6B/coM3474mvhPdW3mBhIKEJZ/bAQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=KUVZXK/QtCfrFTw5xkPpw0UqY1z20JKOYRsl+aSIbPMrvSPpQK2C2iv6dRF0Stib9K hcBBt7FEvj5UmCVnCJIF1VTA2ukl/+UOoMH7qdhPLlGPo7lJtZSqoNGheFw0lP0RIOh3 wcKahsCOvaTzysLg5WdQSw2UX8LPf0K3f4oLs= MIME-Version: 1.0 Received: by 10.210.116.14 with SMTP id o14mr876956ebc.33.1242203226251; Wed, 13 May 2009 01:27:06 -0700 (PDT) In-Reply-To: References: <20090513050333.GA4509@troutmask.apl.washington.edu> From: Chris Rees Date: Wed, 13 May 2009 09:26:46 +0100 Message-ID: To: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Wojciech Puchar , "Anthony M. Rasat" Subject: Re: Disabling ssh timeouts? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 08:27:08 -0000 2009/5/13 Wojciech Puchar : >> >> Read from remote host troutmask.apl.washington.edu: Connection reset by >> peer >> Connection to troutmask.apl.washington.edu closed. >> >> The only way I'v efound to complete a run of the GCC testsuite >> is to sit at the terminal and hit enter every so often. =A0Also > > there is screen program. > 2009/5/13 Anthony M. Rasat : > Steve Kargl wrote: >>I'm trying to running the GCC testsuite, which is not an >>interactive job. Once it starts, it writes to stdout when >>an error occurs or the testsuite moves to a new major > > I think you'd better use screen. First, ssh to your machine, start screen= without any parameter, then start your tests. You can leave ssh afterwards= . Your test will continue to run within your session. > > To continue your last session, just ssh again to that machine and: > > screen -r -x > > Hopefully answers your question. Why have three separate people suggested screen? PLEASE, read the previous posts before repeating what's already there! Chris --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?