Bug 896639

Summary:	systemd keeps starting NetworkManager
Product:	[Fedora] Fedora	Reporter:	Karel Volný <kvolny>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, psimerda, systemd-maint, vpavlin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-17 16:58:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Karel Volný 2013-01-17 16:33:55 UTC

Description of problem:
I have some troubles using NetworkManager, so I need to stop it - just stop it, not to disable it completely. This deosn't work, systemd keeps starting it again and again and again ...

Version-Release number of selected component (if applicable):
systemd-197-1.fc18.1.x86_64

How reproducible:
always

Steps to Reproduce:
1. service NetworkManager stop
2. wait a few (tenths of) seconds
3. service NetworkManager status
  
Actual results:
NM is running

Expected results:
NM is not running

Additional info:

Comment 1 Michal Schmidt 2013-01-17 16:44:15 UTC

Presumably a DBus client of NM causes its reactivation. Does it help if you disable just the DBus activation of NM?:
 rm /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
 systemctl daemon-reload

Comment 2 Pavel Šimerda (pavlix) 2013-01-17 16:58:26 UTC


*** This bug has been marked as a duplicate of bug 815243 ***

Comment 3 Karel Volný 2013-01-17 22:24:50 UTC

(In reply to comment #1)
> Presumably a DBus client of NM causes its reactivation. Does it help if you
> disable just the DBus activation of NM?:
>  rm /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
>  systemctl daemon-reload

bug #815243 comment #19 bullet 2) is the case, I don't want ugly workarounds ...