© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Also this is not really a new bug in upstart. It is related to bug #530779 which causes issues when the parent dies, but its not the same issue, and in fact, the proc connector probably wouldn't help because the proc connector still doesn't solve the problem of knowing when this fork is actually a good one that needs to be followed as the main process versus a fork of a child that just needs to be reaped.
I'm not going to mark it Invalid yet though. I'd like to get some Upstart experts' opinions on whether or not it makes sense to solve this, and really, bug #530779, by simply saying if the process we're tracking forks, then quits, that we should always track the children as the main process.