From owner-freebsd-current Mon Jan 15 13:30:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA10332 for current-outgoing; Mon, 15 Jan 1996 13:30:03 -0800 (PST) Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA10303 for ; Mon, 15 Jan 1996 13:29:58 -0800 (PST) Received: (from vince@localhost) by apollo.COSC.GOV (8.7.3/8.6.9) id NAA10248; Mon, 15 Jan 1996 13:29:59 -0800 (PST) Date: Mon, 15 Jan 1996 13:29:58 -0800 (PST) From: -Vince- To: Robert Sanders cc: "Garrett A. Wollman" , freebsd-current@freebsd.org Subject: Re: finger problem going from 2.1R to -current In-Reply-To: <199601152121.QAA29362@interbev.mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Mon, 15 Jan 1996, Robert Sanders wrote: > On Mon, 15 Jan 1996 16:09:53 -0500, "Garrett A. Wollman" said: > > >> Maybe this can be committed to the tree... > > > No. (There is another, completely different, kernel fix.) > > Yeah, the T/TCP changes just recently got put into the tree. I guess > the importance of T/TCP for this is that it can save, what, one round > trip per finger connection? What confuses me is that, though I > haven't read rfc1644 or the kernel source, I thought that T/TCP would > properly cope with hosts that didn't want to cooperate. > > Otherwise, it seems that the default settings for both rfc* sysctl > options should be off. TCP extensions just seem to cause trouble for > the Average Joe. Yep, atleast on Xyglogics Annex Terminal servers it does... Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin - http://www.COSC.GOV/~vince UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan/Priscilla Chan Fan Club Mailing Lists Admin