Path: utzoo!attcan!uunet!snorkelwacker!spdcc!merk!alliant!cantrell
From: cantrell@Alliant.COM (Paul Cantrell)
Newsgroups: comp.sys.alliant
Subject: Re: job classes
Message-ID: <4059@alliant.Alliant.COM>
Date: 13 Aug 90 14:27:50 GMT
References: <1990Aug10.112530.720@eagle.lerc.nasa.gov>
Reply-To: cantrell@alliant.Alliant.COM (Paul Cantrell)
Organization: Alliant Computer Systems, Littleton, MA
Lines: 20

In article <1990Aug10.112530.720@eagle.lerc.nasa.gov> xxrich@alliant1.lerc.nasa.gov (Rich Rinehart) writes:
>I'm running an intel hypercube simulator and am having trouble getting the
>forked processes it generates to run on individual ce's (they always
>want to run on the complex).  I've tried running the simulator using the
>'execute -ce` command, but any generated processes (it generates a process for
>every node of the hypercube that you simulate) still run on the complex. (?)
>

How about a little more information on how it generates the processes. Does
it simply fork, or does it fork/exec, or does it do a 'system()' call? If
it simply forks, things should be fine. However, if you do an exec of another
executable, that process will then be set to run on the complex if it has
been compiled that way. The same would be true of the unix 'system()' call,
since this actually exec()'s a shell, and then the target.

The easiest thing is probably to just compile the program(s) with -Ogv
so that it generates vector code, but not concurrency code. Then it
should want to run on CE's, instead of complexes.

					PC