Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!netcomsv!feustel From: feustel@netcom.COM (David Feustel) Newsgroups: comp.os.os2.programmer Subject: Re: Killing threads Message-ID: <1991Jun11.213205.16189@netcom.COM> Date: 11 Jun 91 21:32:05 GMT References: <1991Jun8.234338.8440@fwi.uva.nl> <1991Jun9.022029.22896@netcom.COM> <2864@sapwdf.UUCP> Organization: DAFCO - An OS/2 Oasis Lines: 27 wohler@sapwdf.UUCP (Bill Wohler) writes: > to suspend and resume threads, see, oddly enough, DosSuspendThread and > DosResumeThread. >feustel@netcom.COM (David Feustel) writes: >>Absolutely not! No! No! No! Killing threads is against OS/2 rules! > not having a way to do it and being against the rules are two > different things. we hack it by having all of our threads check a > global variable often. when this variable is set, they exit. Actually, you CAN kill ALL threads within an OS/2 process by simply killing the process. What you cannot do is kill a specific thread without killing the process. > osf1 (not os/2) woke up and will provide an api call to kill threads. >-- > --bw >----- >Bill Wohler >Heidelberg Red Barons Ultimate Frisbee Team -- David Feustel, 1930 Curdes Ave, Fort Wayne, IN 46805, (219) 482-9631 EMAIL: feustel@netcom.com or feustel@cvax.ipfw.indiana.edu