Hello, 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 <esta...@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 ‘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' 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, -- rigo http://rigo.altervista.org _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
