Description of problem:
I disable NetworkManager and it still gets bus activated
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. systemctl disable NetworkManager.service
2. start pidgin or thunderbird
3. watch NM get started automatically
NM gets bus activated even if explicitly stopped and disabled
If I manually run systemctl stop NetworkManager.service, I don't really want it auto activated at all. I prefer to not run disable because it disable it permanently while I just want it to stopped for the current session only. Even still, I run systemctl disable NetworkManager.service and it still gets bus activated
Please provide the output of "systemctl dump" after you disabled it.
Created attachment 443234 [details]
systemctl dump output on my system
Args, I know what is wrong.
I don't use NetworkManager on computer, which doesn't have wifi. What's the correct way of disabling NetworkManager?
systemctl disable NetworkManager.service
systemctl enable network.target (because this doesn't have service)
systemctl | grep etwork
NetworkManager.service loaded active running
network.target loaded active active
I suppose there's missing on network.service.
This was discussed at the blocker review meeting of 2010-09-10. We agreed that we would like to accept this bug as a blocker but it does not meet any existing release criterion. We would have to draft a new criterion or set up some integration between the feature and blocker processes to really cover this. (It doesn't even fit in the cop-out paragraph, because we can't reasonably characterize it as a High severity bug: it doesn't make systemd unusable).
For now we will leave it on F14Beta but not mark it as AcceptedBlocker, and try to refine the process. Obviously, it would be best to fix it ASAP regardless :)
Fixed now in git upstream. Upload will follow shortly.
(In reply to comment #6)
> Fixed now in git upstream. Upload will follow shortly.
Great to hear. When will we have a new package in Fedora?
This is not fixed in 10-1, at least not for the case of NetworkManager.
Hm,, this really should be fixed. Are you sure this is still borked? I cannot believe this problem remains, because the code previously responsible for this I removed in its entirety...
Bill, could you please attach "systemctl show Networkmanager.service"?
rpm -q systemd initscripts
After the update, the problem is fixed for me. Thanks. Was such a annoyance.
(In reply to comment #9)
> Hm,, this really should be fixed. Are you sure this is still borked? I cannot
> believe this problem remains, because the code previously responsible for this
> I removed in its entirety...
> Bill, could you please attach "systemctl show Networkmanager.service"?
Well, I've done some more testing... there were still some stray symlinks listing NM as enabled; once those are removed, 'nmcli' no longer starts NM itself.
I still find the behavior pretty odd that 'nmcli nm status' causes networking to start completely,if NM is configured to start on boot but hasn't started yet.
setting back to MODIFIED based on the above.