Comment 6 for bug 92177
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote Re: SIGTERM for re-exec causes problems if Upstart isn't /sbin/init | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Since we just got bitten by this by an upstart package in edgy-updates, it's worth explaining here why we didn't fix this bug at the same time.
There is currently no initctl command for "re-exec yourself", since that relies on code currently in main.c; to add it would involve adding the command itself, and then moving much of the re-exec handling from main.c into control.c -- or a separate module, with both the signal and the control command calling that function.
Also since re-exec is largely empty at the moment, and state isn't transferred, making it a user-visible option would mean more people would try and do it -- which would cause them issues later on. We really need to get state transferrance working.
Not re-exec'ing is also an issue, because the initctl protocol isn't stable (we may just use D-BUS) -- so after an upgrade, initctl would be unable to tell Upstart to reboot or shutdown.
This is still very much on the radar.