Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site investor.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!rochester!cmu-cs-pt!cadre!pitt!darth!investor!rbp
From: rbp@investor.UUCP (Bob Peirce)
Newsgroups: net.unix-wizards
Subject: Re: tar fs copy
Message-ID: <240@investor.UUCP>
Date: Fri, 6-Sep-85 08:04:53 EDT
Article-I.D.: investor.240
Posted: Fri Sep  6 08:04:53 1985
Date-Received: Mon, 9-Sep-85 01:03:50 EDT
References: <832@burl.UUCP> <221@drivax.UUCP> <842@burl.UUCP>
Organization: Cookson, Peirce & Co., Pittsburgh, PA
Lines: 30

> In article <221@drivax.UUCP> alan@drivax.UUCP (Alan Fargusson) writes:
> >You might try tar(1), however you will have to fix it. If you have source
> >that is. As in the example in the manual type:
> >
> >	cd fromdir; tar cf - . | ( cd todir; tar xf - )
> >
> >The problem with this is that when tar tries to make a directory in todir
> >it execs mkdir(1), then waits for ALL of its children to complete. But in
> >the bourne shell the first tar is a child of the second tar, so it can hang
> >forever. All you have to do is fix tar(1) so it only waits for the process
> >that it forked.

Wait a minute!  I have a Bourne shell script called cphier which contains the
following and runs fine.

if [ $# -ne 2 ]
then
	echo usage: cphier frompath topath
fi
exec tar cf - $1 | (cd $2; tar xf - )

What am I doing wrong?
-- 

		 	Bob Peirce, Pittsburgh, PA
		uucp: ...!{allegra, bellcore, cadre, idis}
		  	 !pitt!darth!investor!rbp
				412-471-5320

		NOTE:  Mail must be < 30K  bytes/message