Bug 435642
Summary: | ConsoleKit should be restarted after being updated | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nils Philippsen <nphilipp> |
Component: | ConsoleKit | Assignee: | jmccann |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | cschalle, davidz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-03 02:08:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 435641 | ||
Bug Blocks: |
Description
Nils Philippsen
2008-03-02 21:45:32 UTC
No, for exactly the same reasons we don't restart the system bus daemon or X or the kernel. See lots of discussion on the dbus-list. Acutally, we do restart kernel. Metadata in our repositories can hold an information if an update requires reboot; the same applies to ConsoleKit. (In reply to comment #2) > Acutally, we do restart kernel. Metadata in our repositories can hold an > information if an update requires reboot; the same applies to ConsoleKit. Uhm.. No, we don't restart the kernel (as in kexec'ing into the new kernel keeping user space alive and well). You're thinking about rebooting the system. Which is wildly different. (In reply to comment #3) > (In reply to comment #2) > > Acutally, we do restart kernel. Metadata in our repositories can hold an > > information if an update requires reboot; the same applies to ConsoleKit. > > Uhm.. No, we don't restart the kernel (as in kexec'ing into the new kernel > keeping user space alive and well). You're thinking about rebooting the system. > Which is wildly different. Well, rebooting the system could be interpreted as "restarting the kernel" but that isn't done in all cases either (pup asks the user in that case and only reboots if it is confirmed). Marking a ConsoleKit update to suggest rebooting might be the way to go for now. Without actually checking it, I still think that exec'ing a new ConsoleKit binary while keeping sessions persistent is several orders of magnitude easier than switching the kernel image and keeping the userspace alive and well. I know it's not really on your todo list ;-), but if (big if) I found the time to implement it, would you accept patches to ConsoleKit that implemented exec'ing a new binary while keeping existing sessions, if done properly? (In reply to comment #4) > I know it's not really on your todo list ;-), but if (big if) I found the time > to implement it, would you accept patches to ConsoleKit that implemented > exec'ing a new binary while keeping existing sessions, if done properly? That's up to Jon, he's both the package and upstream maintainer. |