Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site burl.UUCP
Path: utzoo!watmath!clyde!burl!rcj
From: rcj@burl.UUCP (Curtis Jackson)
Newsgroups: net.unix-wizards
Subject: HELP!! (again) -- tar fs copy causes ps screwup
Message-ID: <842@burl.UUCP>
Date: Tue, 3-Sep-85 11:28:55 EDT
Article-I.D.: burl.842
Posted: Tue Sep  3 11:28:55 1985
Date-Received: Wed, 4-Sep-85 06:48:28 EDT
References: <832@burl.UUCP> <221@drivax.UUCP>
Reply-To: rcj@burl.UUCP (Curtis Jackson)
Organization: AT&T Technologies, Burlington NC
Lines: 29
Summary: 

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.

Perhaps one of you can help me with this one:  I did try tar (before I knew
of the problem mentioned above) to copy a filesystem, and it did hang, and
in the process every 'ps -f' (particularly 'ps -ef') I do from that day on
is SCREWED!!  It comes up with all sorts of strange processes with weird
start times and command-names that are random bits of text from the 'fromdir'
filesystem I was trying to tar.  I have tried rebooting with no success;
I have removed /etc/ps_data and let ps recreate it afresh with no success;
I am down now to going through ps with a fine-tooth sdb unless someone can
give me an answer as to where ps is getting this bogus data and how I can
fix it.

Thanks for ANY info re this problem,
-- 

The MAD Programmer -- 919-228-3313 (Cornet 291)
alias: Curtis Jackson	...![ ihnp4 ulysses cbosgd mgnetp ]!burl!rcj
			...![ ihnp4 cbosgd akgua masscomp ]!clyde!rcj