From owner-freebsd-questions@FreeBSD.ORG Wed May 13 14:33:45 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 D065D106568C for ; Wed, 13 May 2009 14:33:45 +0000 (UTC) (envelope-from tcornpropst@cox.net) Received: from eastrmpop107.cox.net (eastrmpop107.cox.net [68.230.240.49]) by mx1.freebsd.org (Postfix) with ESMTP id 51B158FC1E for ; Wed, 13 May 2009 14:33:45 +0000 (UTC) (envelope-from tcornpropst@cox.net) Received: from eastrmimpo03.cox.net ([68.1.16.126]) by eastrmmtao106.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090513141946.CBWT23066.eastrmmtao106.cox.net@eastrmimpo03.cox.net> for ; Wed, 13 May 2009 10:19:46 -0400 Received: from shiloh.cornpropst.net ([72.205.4.251]) by eastrmimpo03.cox.net with bizsmtp id r2Kk1b0025QxCBs022Kkx8; Wed, 13 May 2009 10:19:44 -0400 X-Authority-Analysis: v=1.0 c=1 a=UsaCxHfHPdw0thvUL4kA:9 a=gzij_AhrDNtfYGhAugoA:7 a=6RuOMM8Bo9TioRGCwOKjykloIAcA:4 X-CM-Score: 0.00 Date: Wed, 13 May 2009 10:19:43 -0400 From: "Trevor S. Cornpropst" To: freebsd-questions@freebsd.org Message-ID: <20090513101943.6dc0514a@shiloh.cornpropst.net> In-Reply-To: <20090513050333.GA4509@troutmask.apl.washington.edu> References: <20090513050333.GA4509@troutmask.apl.washington.edu> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.12.11; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Disabling ssh timeouts? 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: Wed, 13 May 2009 14:33:56 -0000 On Tue, 12 May 2009 22:03:33 -0700 Steve Kargl wrote: > Is there anyway to disable sshd from timing out a connection? > I've tried setting ClientAliveCountMax and ClientAliveInterval > and TCPKeepAlive in sshd.conf, but no combination that I've > tried has worked. > > 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 > test category. The last few lines of output are > > Running target unix > Using /usr/X11R6/share/dejagnu/baseboards/unix.exp as board > description file for target. > Using /usr/X11R6/share/dejagnu/config/unix.exp as generic interface > file for target. > Using /usr/home/sgk/gcc/gcc4x/gcc/testsuite/config/default.exp as > tool-and-target-specific interface file. > Running /usr/home/sgk/gcc/gcc4x/gcc/testsuite/gfortran.dg/debug/debug.exp ... > Running /usr/home/sgk/gcc/gcc4x/gcc/testsuite/gfortran.dg/dg.exp ... > > 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. Also > note, nohup and backgrounding the job does not inhibit sshd > dropping the connection and losing all testsuite results. > If you are a csh/tcsh user, you can also 'unset autologout' in your shell and see if that helps. Trevor