From owner-freebsd-questions@freebsd.org Tue May 28 19:16:31 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67FD415A9100 for ; Tue, 28 May 2019 19:16:31 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id D8F598D67B for ; Tue, 28 May 2019 19:16:30 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from lowell-desk.be-well.ilk.org (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id C663633C58 for ; Tue, 28 May 2019 15:16:24 -0400 (EDT) Received: by lowell-desk.be-well.ilk.org (Postfix, from userid 1147) id 34DF7187EE8; Tue, 28 May 2019 15:16:23 -0400 (EDT) From: Lowell Gilbert To: freebsd-questions@freebsd.org Subject: Re: ssh timeout question References: Reply-To: freebsd-questions@freebsd.org Date: Tue, 28 May 2019 15:16:23 -0400 In-Reply-To: (Doug Denault's message of "Tue, 28 May 2019 14:42:22 -0400 (EDT)") Message-ID: <44imtu8k54.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: D8F598D67B X-Spamd-Bar: +++++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [7.43 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[freebsd-questions@freebsd.org]; GREYLIST(0.00)[pass,meta]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.34)[0.344,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[ilk.org]; MX_GOOD(-0.01)[cached: be-well.ilk.org]; NEURAL_SPAM_LONG(1.00)[0.999,0]; NEURAL_SPAM_MEDIUM(0.06)[0.058,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7922, ipnet:23.30.0.0/15, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.09), ipnet: 23.30.0.0/15(0.07), asn: 7922(0.10), country: US(-0.06)]; REPLYTO_EQ_TO_ADDR(5.00)[] X-Spam: Yes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 19:16:31 -0000 Doug Denault writes: > On Tue, 28 May 2019, RW via freebsd-questions wrote: > >> I doubt it's to do with timing out an idle connection since pine is >> polling for new mail ever 150s. > > Thank you all for comments and suggestions. It would not have occurred > to me to set the keep-alive value that small, I will try that. That is > a lot less irritating than my print a char script that mucks up > emails. In google I found someone suggesting setting "IPQoS > throughput" in $HOME/.ssh/config. I am going to try both when I next > go to a 100% fail location. I'll report back. > > I also find it strange that sitting in pine triggers the timeout but > sitting idle for days does not. I don't run into issues with this because my remote sessions tend to have an application running that updates an on-screen time display every minute. That's not why I do it, of course.