Bug 896639 - systemd keeps starting NetworkManager
Summary: systemd keeps starting NetworkManager
Keywords:
Status: CLOSED DUPLICATE of bug 815243
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-17 16:33 UTC by Karel Volný
Modified: 2013-01-17 22:24 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-17 16:58:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ...


Note You need to log in before you can comment on or make changes to this bug.