Bug 509523 - Can't turn off NM
Can't turn off NM
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
11
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-03 05:38 EDT by Peter Vrabec
Modified: 2009-11-10 20:27 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-11-10 20:27:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Vrabec 2009-07-03 05:38:21 EDT
Description of problem:

What can I expect from 
#  chkconfig NetworkManager --list
NetworkManager  0:off   1:off   2:off   3:off   4:off   5:off   6:off

Actual results:
/var/log/messages
Jul  3 10:50:24 wrabco nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Jul  3 10:50:26 wrabco nm-system-settings:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-br0 ...
Jul  3 10:50:26 wrabco nm-system-settings:    ifcfg-rh:     error: Unknown connection type 'Bridge'
Jul  3 10:50:26 wrabco nm-system-settings:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ...
Jul  3 10:50:27 wrabco nm-system-settings:    ifcfg-rh:     read connection 'System eth0'
Jul  3 10:50:27 wrabco nm-system-settings:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...

# ps aux | grep  nm-system
root      2515  0.0  0.2  78280  4236 ?        S    10:50   0:00 /usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf

Expected results:
empty logs
no process
Comment 1 Dan Williams 2009-11-10 20:27:46 EST
That's just nm-system-settings, which will auto-launch when the applet or nm-connection-editor is running.  That's not NetworkManager itself.

In any case, this is gone with Fedora 12/NM 0.8 where nm-system-settings is integrated into NetworkManager, and NM doesn't get autolaunched at all like nm-system-settings did.

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