From owner-freebsd-hackers Thu Nov 19 06:01:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03320 for freebsd-hackers-outgoing; Thu, 19 Nov 1998 06:01:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03313 for ; Thu, 19 Nov 1998 06:01:31 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id OAA01700 for ; Thu, 19 Nov 1998 14:00:58 GMT Message-ID: <3654249A.6794F460@tdx.co.uk> Date: Thu, 19 Nov 1998 14:00:58 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Dump - odity on network connections? (netcat) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it me, or does Dump behave 'oddly' when running through network connections such as 'netcat'? I have to set timeouts for the netcat connection, else even when Dump has finished (and presumably closed it's connections) netcat/dump just hangs around ad infinitum... I've had a quick look through the source, but it's a little beyond me - I also seem to remember someone in the dim distant past mentioning this? (Searching the archives for 'dump' was not such a good idea :-) -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message