Date: Tue, 23 Aug 2016 13:09:26 +0200 From: Arrigo Marchiori <ardovm@yahoo.it> To: schmidt@ze.tum.de Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Problems with piped tar Message-ID: <20160823110926.GB76750@nuvolo> In-Reply-To: <6a841a00-6765-f1a2-02c3-9ce87ec595e8@ze.tum.de> References: <96b7f57f-74ac-9445-1d04-61327ab111dc@ze.tum.de> <E0606B64-AF3A-4FB9-BCF8-9F7C7AE85FE7@cs.huji.ac.il> <6a841a00-6765-f1a2-02c3-9ce87ec595e8@ze.tum.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On Tue, Aug 23, 2016 at 09:35:12AM +0200, Gerhard Schmidt wrote: > Am 23.08.2016 um 09:18 schrieb Daniel Braniss: > >=20 > >> On 23 Aug 2016, at 10:06, Gerhard Schmidt <estartu@ze.tum.de> wrote: > >> > >> Hi, > >> > >> i'm quite often use tar to copy files using > >> > >> tar cf - /some/dir | (cd /dest/dir; tar xvvf - ) > > the =E2=80=98new=E2=80=99 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=E2=80=99t > > include /. >=20 > 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 en= d > of nc or just a '> file.tar' Maybe you are not invoking nc(1) with the -N option? >From the manual page: >>>> -N shutdown(2) the network socket after EOF on the input. = Some >>>> servers require this to finish their work. I hope this helps. Regards, --=20 rigo http://rigo.altervista.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160823110926.GB76750>