Issue 39390 - soffice doesn't terminate child prozesses
Summary: soffice doesn't terminate child prozesses
Status: CLOSED DUPLICATE of issue 62312
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: hennes.rohling
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-21 12:26 UTC by b.osi.ooo
Modified: 2008-11-05 20:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description b.osi.ooo 2004-12-21 12:26:36 UTC
before the src680m65 it worked;

currently I see 2 different prozesses on Unix:
soffice and a list of soffice.bin's
on win32:
soffice.BIN and soffice.exe

the first prozess is: soffice / soffice.exe, that was started by the user or
testtool application

So if I terminate these prozess (soffice or soffice.exe), I expect that the
prozesses, that were started by these programms get terminated, too.

BUG: But it doesn't.
Formaly it worked this way;

But you may also come up with a workaround for the following situation:
start soffice -> I get the prozessid, that formaly invoked with 'kill' terminates
all soffice prozesses;
Where do I nowadays get a working prozessID, that terminates all soffice prozesses?

(In testtool exists the command 'killapp', at least that has to work this way.)
Comment 1 b.osi.ooo 2004-12-21 14:01:09 UTC
.
Comment 2 hennes.rohling 2005-01-06 11:01:53 UTC
Currently you have to kill the soffice.bin process (both Windows and Unix). For
Unix you need to call the 'ps' command to obtain the PID of the soffice.bin
process. The PID that is printed to the terminal is the PID of the shell wrapper
process 'soffice'.
Comment 3 hennes.rohling 2005-02-11 13:04:06 UTC
As this is mainly a problem of the testtool, this will be handled by
osl_terminateProcess.
Comment 4 christof.pintaske 2005-03-04 12:28:49 UTC
we cannot do it on 2.0 anymore
Comment 5 christof.pintaske 2005-05-25 13:42:13 UTC
Retargeted to Office Later, due to lack of resources we have to concentrate on
the most relevant issues for the next micro update.
Comment 6 kai.sommerfeld 2008-07-23 14:31:34 UTC
duplicate.

*** This issue has been marked as a duplicate of 62312 ***
Comment 7 Mechtilde 2008-11-05 20:31:35 UTC
close the duplicate