From owner-freebsd-newbies@FreeBSD.ORG Sat Nov 20 21:13:10 2004 Return-Path: Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AE5316A4D0 for ; Sat, 20 Nov 2004 21:13:10 +0000 (GMT) Received: from flabnapple.net (Flabnapple.Net [204.87.183.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id D25DE43D4C for ; Sat, 20 Nov 2004 21:13:09 +0000 (GMT) (envelope-from lists@rzweb.com) Received: from [10.0.1.3] (c-24-5-6-87.client.comcast.net [24.5.6.87]) by flabnapple.net (8.12.8/8.12.8) with ESMTP id iAKLD5JP022193 for ; Sat, 20 Nov 2004 13:13:05 -0800 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ron Gilbert Date: Sat, 20 Nov 2004 13:12:50 -0800 To: freebsd-newbies@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: sshd timeout X-BeenThere: freebsd-newbies@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Gathering place for new users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 21:13:10 -0000 I think this is my fault some how. It works on my other server with: ClientAliveInterval=15 ClientAliveCountMax=3 so I must have something else conflicting with it. Ron On Nov 20, 2004, at 9:36 AM, Ron Gilbert wrote: > I am trying to figure out how to keep a remote ssh session from being > timed out by my FreeBSD (5.3) server. > > I've done a lot of searching on the subject, and everyone points to > ClientAliveInterval, ClientAliveCountMax and KeepAlive in sshd_config. > Problem is, these setting don't help since they seem to be about > connections closing, not leaving a terminal session idle. > > My problem is I've ssh'd in from my Mac to my FreeBSD server, and I > need that ssh window to stay open forever. Right now it closes after > about 30 minutes of nothing being sent either way. > > Sometimes I get a "Connection closed" error, and sometimes the Mac > terminal window just hangs and I have to close it. I have the same > problem when shh'ing in from a Windows machine using Putty, except > Putty has a option to send NUL chars every X minutes to keep the > session alive, which works, but I would rather just keep the server > from timing it out, and I don't use a Widows machine anymore. > > Is there a way to fix this? > > Ron > > > _______________________________________________ > freebsd-newbies@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-newbies > To unsubscribe, send any mail to > "freebsd-newbies-unsubscribe@freebsd.org"