Bug 726313

Summary:	disable dhcpd ,but after reboot ,dhcpd also started
Product:	[Fedora] Fedora	Reporter:	frank ling <ufwt>
Component:	dhcp	Assignee:	Jiri Popelka <jpopelka>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jpopelka
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-02 10:14:10 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 frank ling 2011-07-28 07:52:06 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. /bin/systemctl disable dhcpd.service
2. reboot
3. ps -ef | grep dhcpd
  
Actual results:
have dhcpd process

Expected results:
no dhcpd process

Additional info:

Comment 1 frank ling 2011-07-29 09:21:55 UTC

i think maybe 
/etc/NetworkManager/dispatcher.d/12-dhcp have error

Comment 2 Jiri Popelka 2011-08-11 14:20:57 UTC

(In reply to comment #1)
> i think maybe 
> /etc/NetworkManager/dispatcher.d/12-dhcp have error

Thanks for the report, however it works for me.

There was a bug #699027 in systemd when systemctl reported service as enabled while it was disabled. But this problem should be fixed already.

What does 'rpm -q systemd' say ?

And what show these commands:
 systemctl disable dhcpd.service; echo $?
 systemctl is-enabled dhcpd.service; echo $?

Comment 3 Jiri Popelka 2012-04-02 10:14:10 UTC

I'm closing this ticket because it has not been updated by the submitter for almost 8 months. If the issue still requires resolution, please re-open.