Bug 460574
Summary: | dbus can't start in chroot | ||
---|---|---|---|
Product: | [Retired] Fedora Hosted Projects | Reporter: | Andrew Overholt <overholt> |
Component: | mock | Assignee: | Clark Williams <williams> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | dcantrell, walters |
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: | 2010-07-27 18:47:42 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: |
Description
Andrew Overholt
2008-08-28 18:57:39 UTC
I don't have any fundamental objection to having the ability to use dbus in the chroot, but I wonder if there are going to be any side effects of having (at least) two dbus daemons running on a system? There's normally at least two - the system bus and the per-user session bus. This patch simply enables the session bus to run; there should be no effect whatsoever on the rest of the OS. Starting a system bus in the chroot is a different matter and while it would likely mostly work I would strongly discourage people from doing that. But this bug was about the session. Ugh, I missed this in the 0.9.14 spin. queued for 0.9.15 |