[openbeos] Re: popen() alternatives
- From: "Bruno G. Albuquerque" <bga@xxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 20 Jul 2003 14:48:42 -0300 EST
On Sun, 20 Jul 2003 17:47:47 +0200 CEST, Jonas Sundstrom said:
> And it needs to be thread-safe, so, IIRC, no fork()'ing.
> (there will be BLoopers around)
Then you have a problem. popen() uses fork() internally.
> So, what are the alternatives to popen() that allows
> reading and killing?
>
> Is there a pkill()?
If you can determine the team id of the process you launched you can
just kill the process by yourself. Supposing you did call pclose()
before killing the process (pclose() will block until the process
terminates) there will be no problem I guess. Except for what I
mentioned above.
-Bruno
--
Fortune Cookie Says:
Never eat more than you can lift.
-- Miss Piggy
--
Fortune Cookie Says:
The opossum is a very sophisticated animal. It doesn't even get up
until 5 or 6 p.m.
--
Fortune Cookie Says:
Remember, drive defensively! And of course, the best defense is a good
offense!
--
Fortune Cookie Says:
"No one gets too old to learn a new way of being stupid."
- References:
- [openbeos] popen() alternatives
- From: Jonas Sundstrom
Other related posts:
- » [openbeos] popen() alternatives
- » [openbeos] Re: popen() alternatives
- » [openbeos] Re: popen() alternatives
- » [openbeos] Re: popen() alternatives
- » [openbeos] Re: popen() alternatives
- [openbeos] popen() alternatives
- From: Jonas Sundstrom