Date: Tue, 23 Aug 2016 10:58:26 +0300 From: Daniel Braniss <danny@cs.huji.ac.il> To: schmidt@ze.tum.de Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Problems with piped tar Message-ID: <85AD8196-B2C7-46AC-B9D2-68C71DF1824C@cs.huji.ac.il> 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
> On 23 Aug 2016, at 10:35, Gerhard Schmidt <estartu@ze.tum.de> wrote: >=20 > 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: >>>=20 >>> Hi, >>>=20 >>> i'm quite often use tar to copy files using >>>=20 >>> 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 = end > of nc or just a '> file.tar=E2=80=99 >=20 try with different shells. (sh/bash/csh/zsh/=E2=80=A6) > Regards > Estartu >=20 >=20 >=20 > --=20 > ------------------------------------------------- > Gerhard Schmidt | E-Mail: schmidt@ze.tum.de = <mailto:schmidt@ze.tum.de> > TU-M=C3=BCnchen | Jabber: estartu@ze.tum.de = <mailto:estartu@ze.tum.de> > WWW & Online Services | > Tel: 089/289-25270 | > Fax: 089/289-25257 | PGP-Publickey auf Anfrage
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85AD8196-B2C7-46AC-B9D2-68C71DF1824C>