Bug 22821 - networkmanager starts when disabled
Summary: networkmanager starts when disabled
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-24 07:59 CET by Christian Müller
Modified: 2020-08-02 22:12 CEST (History)
4 users (show)

See Also:
Source RPM: networkmanager-1.8.6-1.mga6, systemd
CVE:
Status comment:


Attachments

Description Christian Müller 2018-03-24 07:59:36 CET
Description of problem:

networkmanager.service starts although when it is disabled

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

networkmanager-1.8.6-1.mga6

How reproducible:

console output:

# systemctl status networkmanager.service 
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset:
   Active: active (running) since Sa 2018-03-24 07:52:27 CET; 12s ago
     Docs: man:NetworkManager(8)
 Main PID: 25272 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           └─25272 /usr/sbin/NetworkManager --no-daemon

# systemctl stop networkmanager.service 
# systemctl disable networkmanager.service 
Removed /etc/systemd/system/multi-user.target.wants/NetworkManager.service.
Removed /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service.
Removed /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service.

#systemctl status networkmanager.service 
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset
   Active: inactive (dead) since Sa 2018-03-24 07:53:08 CET; 1min 12s ago
     Docs: man:NetworkManager(8)
 Main PID: 25272 (code=exited, status=0/SUCCESS)

# systemctl start networkmanager.service 
# systemctl status networkmanager.service 
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset
   Active: active (running) since Sa 2018-03-24 07:54:49 CET; 3s ago
     Docs: man:NetworkManager(8)
 Main PID: 25506 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           └─25506 /usr/sbin/NetworkManager --no-daemon

After reboot, networkmanager is running although it is disabled and has to be stopped. Background: I can't establish any WiFi connection with networkmanager running, but that's another story.
Marja Van Waes 2018-03-24 08:57:12 CET

CC: (none) => marja11, ngompa13
Assignee: bugsquad => basesystem
Source RPM: networkmanager-1.8.6-1.mga6 => networkmanager-1.8.6-1.mga6, systemd

Comment 1 Frank Griffin 2018-03-24 13:48:54 CET
"disabled" means it shouldn't be started at boot, not that it can't be started.  So none of what you show is unusual except for the claim that  it was started at boot while disabled.  What does "status" show then ?

Also note that many packages assume that if they're installed they ought to be enabled, and will re-enable themselves if updated (mysqld comes to mind).

CC: (none) => ftg

Comment 2 Christian Müller 2018-04-03 20:48:43 CEST
(In reply to Frank Griffin from comment #1)
> "disabled" means it shouldn't be started at boot, not that it can't be
> started.  So none of what you show is unusual except for the claim that  it
> was started at boot while disabled.  What does "status" show then ?

ok, had a little time last weekend and did some testing: status shows 'disabled', but service gets startet on boot-up. I reproduced that on three machines.

> Also note that many packages assume that if they're installed they ought to
> be enabled, and will re-enable themselves if updated (mysqld comes to mind).

That was the case, and I set the service to 'disabled' after update.
Comment 3 Aurelien Oudelet 2020-08-02 22:12:41 CEST
Hi,

Currently, disabling a systemd unit is not the recommended way to prevent it from being restarted at boot.

You must mask it:

# systemctl stop foo.service
# systemctl disable foo.service
# systemctl mask foo.service

Also, this message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

CC: (none) => ouaurelien
Resolution: (none) => OLD
Status: NEW => RESOLVED


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