From owner-freebsd-hackers Wed Mar 25 08:29:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04803 for freebsd-hackers-outgoing; Wed, 25 Mar 1998 08:29:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04779 for ; Wed, 25 Mar 1998 08:29:30 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id LAA17349; Wed, 25 Mar 1998 11:29:11 -0500 (EST) Date: Wed, 25 Mar 1998 11:29:11 -0500 (EST) From: Snob Art Genre To: Arman Hazairin cc: dg@root.com, freebsd-hackers@FreeBSD.ORG Subject: Re: TCP connection hang In-Reply-To: <35190E33.7E908938@ai3.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Mar 1998, Arman Hazairin wrote: > Btw, I convert the binary file that i want to transmit into text using > uuencode, and finaly i can transfer the file. Perhaps you could split(1) the file into two parts, and see which one causes the transfer to hang. Then rinse, repeat, until you've isolated the byte sequence of death. That should be illuminating. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message