Bug 163711
Summary: | dhcdbd startup issues | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Colin Walters <walters> |
Component: | dhcdbd | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dcbw, dwalsh, erikj, johnp, laroche, pierre-bugzilla, prarit, sundaram |
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: | 2005-09-05 00:05:11 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
Colin Walters
2005-07-20 15:59:57 UTC
*** Bug 162857 has been marked as a duplicate of this bug. *** The recommended configuration for dhcdbd at the moment is NOT to start it from the initscript, but to let NetworkManager start it (the dhcdbd.spec file does NOT do a 'chkconfig --add'), and if dhcdbd is not running, NetworkManager starts it up. I'll resolve this issue next week with dhcdbd-1.7, at the same time as resolving the issue of whether dhcdbd should auto-start on the session bus and authentication issues. I'm confused why dhcdbd has an init script at all if it's not intended to be run by the init system. In fact if this is the recommended usage why is it even a separate package from NetworkManager? Having NetworkManager execute it currently conflicts with the Fedora SELinux policy for it; I've added dwalsh to the CC here. If having NetworkManager exec dhcdbd is the route chosen then we need to get policy updated to do a domain transition. domain_auto_trans(NetworkManager_t, dhcpc_exec_t, dhcpc_t) Is already in there. RE: Comment #3: dhcdbd is intended to be a general-purpose program for controlling dhclient, and providing access to dhcp options and notifications of dhcp option change to any subscribing application, not just NetworkManager - hence the initscript. Yes, I know there is a problem with the chkconfig startup order number - As I said earlier, I'll be fixing that in the next release next week, along with the authentication issues . The SELinux policy is working correctly for it. This is now fixed with dhcdbd-1.7, now in Rawhide and on external CVS. The initscript now has 'chkconfig: 345 98 02', the same as NetworkManager, and will start after the messagebus has started. The system.d/dhcdbd.conf policy configuration now disallows any user other than root to send to dhcdbd. Might go into a new bugzilla: /etc/init.d/dhcdbd: line 14: /etc/sysconfig/network: No such file or directory RE: Comment #7 This is now fixed with dhcdbd-1.8. I saw comment #7 during initial install of FC ia64 development. But dhcdbd in development for ia64 hasn't bumped to dhcdbd-1.8 yet. ia64 is at dhcdbd-1.7-1. Adding myself to the cclist. RE: Comment #9: sorry about that. dhcdbd-1.8 is now in rawhide / development. |