From owner-freebsd-stable@freebsd.org Tue Aug 23 11:31:59 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32776BC3BE7 for ; Tue, 23 Aug 2016 11:31:59 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0FDB1DB8 for ; Tue, 23 Aug 2016 11:31:58 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bc9vv-0008YL-Si; Tue, 23 Aug 2016 12:31:56 +0100 Date: Tue, 23 Aug 2016 12:31:55 +0100 From: Gary Palmer To: Gerhard Schmidt Cc: Daniel Braniss , freebsd-stable Subject: Re: Problems with piped tar Message-ID: <20160823113155.GB56297@in-addr.com> References: <96b7f57f-74ac-9445-1d04-61327ab111dc@ze.tum.de> <6a841a00-6765-f1a2-02c3-9ce87ec595e8@ze.tum.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6a841a00-6765-f1a2-02c3-9ce87ec595e8@ze.tum.de> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2016 11:31:59 -0000 On Tue, Aug 23, 2016 at 09:35:12AM +0200, Gerhard Schmidt wrote: > Am 23.08.2016 um 09:18 schrieb Daniel Braniss: > > > >> On 23 Aug 2016, at 10:06, Gerhard Schmidt wrote: > >> > >> Hi, > >> > >> i'm quite often use tar to copy files using > >> > >> tar cf - /some/dir | (cd /dest/dir; tar xvvf - ) > > the ???new??? way: > > tar cf - /some/dir | tar xvvd - -C /dest/dir > > which of course does not explain way your version hangs, but this one is cleaner, and btw, don???t > > include /. > > that's very strange. It's working, but doesn't solve another related > problem. When i pipe the tar thru nc a have the same problem as my > version. And it's no difference if there is a tar c an the receiving end > of nc or just a '> file.tar' Is the sending side using nc -N ? If not, the sending socket is not being shut down. Regards, Gary