From owner-freebsd-hackers Fri Mar 17 18:35:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA05920 for hackers-outgoing; Fri, 17 Mar 1995 18:35:23 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA05913 for ; Fri, 17 Mar 1995 18:35:20 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA26779 (5.67a/IDA-1.5); Fri, 17 Mar 1995 20:17:48 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA02479; 17 Mar 95 19:51:13 CST (Fri) Received: from localhost (localhost [127.0.0.1]) by bonkers.taronga.com (8.6.8/8.6.6) with SMTP id TAA02475; Fri, 17 Mar 1995 19:51:13 -0600 Message-Id: <199503180151.TAA02475@bonkers.taronga.com> X-Authentication-Warning: bonkers.taronga.com: Host localhost didn't use HELO protocol To: "Charles M. Hannum" Cc: terry@cs.weber.edu, hackers@FreeBSD.org, tech-net@netbsd.org Subject: Re: Batch Telnet (Re: diskless and 3Com 509) In-Reply-To: Your message of "Fri, 17 Mar 95 10:58:46 EST." <199503171558.KAA27534@duality.gnu.ai.mit.edu> X-Mailer: exmh version 1.4.1 7/21/94 Date: Fri, 17 Mar 1995 19:50:27 -0600 From: Peter da Silva Sender: hackers-owner@FreeBSD.org Precedence: bulk The interesting thing is that the System V telnet client doesn't seem to be doing the same thing. If it's doing a "half close" how is the close getting propogated to the other end if TCP/IP doesn't implement it? Since the other end in the case of nntpd or other plain TCP servers isn't implementing the full telnet protocol it doesn't seem like it could be using some obscure telnet option to get this effect. > The telnet client should at least have an option to not shut down if > it gets EOF from stdin. It's not clear to me whether or not that > should be the default. I'm leary of making it the default, because otherwise you get the classic infinite loop on EOF problem too easily.