Code review comment for lp://staging/~clint-fewbar/ubuntu/natty/upstart/restore-re-exec-code
Revision history for this message
| Colin Watson (cjwatson) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
This basically seems OK; but one possible failure mode comes to mind. If the old libc6.postinst is run with the new upstart, then it will run 'telinit u' and that will send SIGTERM to upstart, which will faithfully re-exec and will now have no job state. Is it worth adding some kind of packaging metadata, perhaps Breaks, to try to avoid that?