Are you using the /B parameter? The help file says that this disables ^C processing
hth Jon On 12 September 2015 at 22:28, CVBruce <[email protected]> wrote: > And how would the system know which process you are trying to terminate? > > Sent by Magic! > > > On Sep 12, 2015, at 1:28 PM, Bertram Moshier <[email protected]> > wrote: > > > > Hi, > > > > OK, maybe I'm jumping the gun as I have yet to come up with a simple > test, but . . . This issue may affect everyone who starts multiple > processes using ooRexx. > > > > What I noticed is when I have an ooRexx program start other > processes/session using the start command, I'm unable to kill them using > Control-C. Thus when you start other processes to use a multiple cores or > more than one physical processor, you can't terminate them with control-C > should something go wrong (or if by desire that is how you want to > terminate the process). > > > > Am I just old fashion or is there a better way to write multiple > threaded / multiple processor ooRexx programs than to "spin"/"fork"/"start" > other Command Prompt sessions and then communicate via pipes, queues, etc? > > > > Thanks in advance for helping this old folk with his programming, > > > > Bert. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Oorexx-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > > ------------------------------------------------------------------------------ > _______________________________________________ > Oorexx-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-users >
------------------------------------------------------------------------------
_______________________________________________ Oorexx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-users
