Date: Sat, 20 Nov 2004 13:12:50 -0800 From: Ron Gilbert <lists@rzweb.com> To: freebsd-newbies@freebsd.org Subject: Re: sshd timeout Message-ID: <EF5DD56A-3B38-11D9-86BA-000D93B0A5F4@rzweb.com> In-Reply-To: <B539FF70-3B1A-11D9-9CF0-000D93B0A5F4@rzweb.com> References: <B539FF70-3B1A-11D9-9CF0-000D93B0A5F4@rzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EF5DD56A-3B38-11D9-86BA-000D93B0A5F4>