Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!jpl-devvax!jato!jdickson
From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: HELP with Independant Children Processes
Message-ID: <1991Feb6.190231.1116@jato.jpl.nasa.gov>
Date: 6 Feb 91 19:02:31 GMT
References: <1991Feb4.171549.28531@nntp-server.caltech.edu> <Jay.9138@deepthot.UUCP>
Reply-To: jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 15

In article <Jay.9138@deepthot.UUCP> Jay@deepthot.UUCP (Jay Denebeim) writes:
>In article <1991Feb4.171549.28531@nntp-server.caltech.edu> tll@nntp-server.caltech.edu (Tal Lewis Lancaster) writes:
>>I have the following requiremnts:
>>
>>A parent process that starts up children processes and waits for them
>>before continuing.  The child might require up to 50 arguments.  These
>>arguments concatenated togther could total 1000 characters.  The parent
>>needs to know if the child succeeded or failed (ie. returns 0 if okay,
>>anything else if failed).  Here's the catch the child must be an independant
>>program capable of being run on its own from CLI (just like COPY, MAKEDIR, etc.)
>
	IMHO, System() and Execute() are gross, because of the overhead invol-
ved. It's not all that difficult to use LoadSeg() and CreateProc(). Besides
parameters can be passed to the child process via the tc_UserData field in the 
task control block.