From owner-freebsd-current@FreeBSD.ORG Tue Jun 8 12:27:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2496316A4E2 for ; Tue, 8 Jun 2004 12:27:54 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E8343D45 for ; Tue, 8 Jun 2004 12:27:53 +0000 (GMT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i58CRbrv010869; Tue, 8 Jun 2004 16:27:37 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i58CRati010868; Tue, 8 Jun 2004 16:27:36 +0400 (MSD) (envelope-from ache) Date: Tue, 8 Jun 2004 16:27:35 +0400 From: Andrey Chernov To: Stephen McKay Message-ID: <20040608122735.GA10813@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Stephen McKay , freebsd-current@FreeBSD.ORG References: <200406081157.i58BvGJd012588@dungeon.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406081157.i58BvGJd012588@dungeon.home> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.25.0.61; VDF 6.25.0.87 (host: pobrecita.freebsd.ru) cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd should not use TCP_NODELAY X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2004 12:27:54 -0000 On Tue, Jun 08, 2004 at 09:57:16PM +1000, Stephen McKay wrote: > My quick and ready answer to my problem is to hack openssh/packet.c and take > out the call to set_nodelay() from packet_set_interactive(). This means that > TCP_NODELAY is no longer set on the socket. It also turns it off in the client > but I may change my mind on that yet. Just FYI, PuTTY client have an option to enable/disable TCP_NODELAY per user needs. If it will be an option, it should go to client part too. -- Andrey Chernov | http://ache.pp.ru/