Date: Thu, 16 Mar 1995 19:33:04 -0600 (CST) From: Peter da Silva <peter@bonkers.taronga.com> To: terry@cs.weber.edu (Terry Lambert) Cc: hackers@FreeBSD.org Subject: Re: Batch Telnet (Re: diskless and 3Com 509) Message-ID: <199503170133.TAA08481@bonkers.taronga.com> In-Reply-To: <9503170051.AA26101@cs.weber.edu> from "Terry Lambert" at Mar 16, 95 05:51:09 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> It is not a question of the telnet waiting for the other side to flush > output before going away. It is a question of the telnetd (in your > example, the nntpd) waiting for the output to be flushed to your > machine before sending the disconnect. > The problem is in the server, not the client. *really*? That's surprising... I'm sure I did the same thing from System V to the same client program. Especially when the following works: (echo LIST; echo QUIT; sleep 600000) | telnet localhost nntp I don't see how *server* side behaviour can explain this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503170133.TAA08481>