Bug 3907 - FryskHelpManager uses Runtime.exec
Summary: FryskHelpManager uses Runtime.exec
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 3398
  Show dependency tree / graph
 
Reported: 2007-01-23 17:21 UTC by Andrew Cagney
Modified: 2007-01-26 14:54 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2007-01-23 17:21:47 UTC 
The problem with Runtime.exec is that it uses "SIGCHLD" and waitpid to clean up
after the created subprocess.  Since frysk is also managing those kernel
interfaces a chash occures.

Instead the code should more directly use frysk.sys.Fork.exec or similar to
create the child process.
Comment 1 Andrew Cagney 2007-01-23 17:29:23 UTC 
The method frysk.sys.Fork.daemon() would be best as it re-parents the process to
not be frysk.

Of course, this also has the disadvantage of not being able to determine when
the program fails to start.
Comment 2 Rick Moseley 2007-01-26 14:54:24 UTC 
Converted to use frysk.sys.Fork.daemon().  Now causes backtraces on initial
activation.  This has been enumerated in bz #3927.