Thus it was written in the epistle of Steve Dirickson,
>
> No, that isn't what it means; ACTIVATE(x, 0) simply means (not in OS
> specifics, but in concepts) "move process x from the suspended list to the
> runnable list". Execution of the caller continues normally until it reaches
> the end of its quantum, initiates I/O, or does something else to cause the
> scheduler to run some other process. Eventually, that "other process" will
> be "x".

Oh, ok.

> You may be thinking of a parent process that creates/activates a child and
> indicates in a CREATEPROCESS, ACTIVATE, or SUSPEND call that it wants to be
> suspended until the child activates it; such a parent will be activated when
> the child terminates, even if the child does nothing to activate the parent.

Nope.  You give me too much credit :-).  It's just that I tried the
ACTIVATE(pin,0) and the child process didn't proceed until after I had typed
EXIT in the parent process and the parent process had completed.  That is, the
parent returned to a user input but the child didn't run then--it ran when the
parent had exited.  Thus my rash conclusion that the ,0 option put the child
as the next thing to run after the parent.

> > I'm needing
> > the child process to do its cleanup and get out of the way
> > prior to the parent
> > process ending, so that doesn't happen to solve my needs
>
> Actually it does: just call ACTIVATE(childpin, 0). The child will
> (eventually) wake up, do its cleanup, and terminate. If the parent needs to
> wait until the child finishes its cleanup, use ACTIVATE(childpin, 2) and
> have the child call ACTIVATE(0, 0) just before it exits.

Makes sense, thanks.

Ted
--
Ted Ashton ([log in to unmask]), Info Sys, Southern Adventist University
          ==========================================================
It is a good thing for an uneducated man to read books of quotations.
                                -- Churchill, [Sir] Winston Spencer (1874-1965)
          ==========================================================
         Deep thought to be found at http://www.southern.edu/~ashted

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *