[BusyBox] (Ash) 'exec' starts a new tread
az1 at zastrow4u.de
Mon Oct 6 20:07:52 UTC 2003
I'm fighting with a different behavior of ash compared to bash:
If I start something within a shellscript with 'exec' ash generates a
new pid and the child seems to be independent from the father-process,
even if you kill the father job.
When you do the same thing (exec) with bash, the child takes over the pid.
Right now I don't know a solution for killing a exec'ed child if I know
only the pid from its father :-(
More information about the busybox