From owner-freebsd-current Fri May 15 19:16:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17592 for freebsd-current-outgoing; Fri, 15 May 1998 19:16:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17587 for ; Fri, 15 May 1998 19:16:46 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id WAA04061; Fri, 15 May 1998 22:16:44 -0400 (EDT) (envelope-from wollman) Date: Fri, 15 May 1998 22:16:44 -0400 (EDT) From: Garrett Wollman Message-Id: <199805160216.WAA04061@khavrinen.lcs.mit.edu> To: Guido van Rooij Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/libexec/fingerd fingerd.c In-Reply-To: <199805152301.BAA03572@gvr.gvr.org> References: <199805150323.UAA10174@freefall.freebsd.org> <199805152301.BAA03572@gvr.gvr.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > With the code I committed to inetd, you can get actually completely > delete the NOPUSH code, and specify tcp/ttcp in inetd. However, > I was under the impression that fingerd no longer has TCP_NOPUSH > enabled by default!? No, there was never any reason why it should be disabled in fingerd. All TCP_NOPUSH does is prevent the sender-TCP from sending out tinygrams in the name of write boundary preservation. In the case of fingerd, what that meant was that the entire reply was usually buffered until the socket was closed. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message