You are not logged in.
Pages: 1
Hello all, I got all this services enabled. A lot of them are related to network... but who can I know if this services are overlapping or not?
$ systemctl list-unit-files --type=service | grep enabled
autovt@.service enabled
bluetooth.service enabled
cups-browsed.service enabled
dbus-org.bluez.service enabled
dbus-org.freedesktop.network1.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
docker.service enabled
gdm.service enabled
getty@.service enabled
lm_sensors.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager.service enabled
systemd-networkd.service enabled Web Developer.
Arch x64 on Aspire S3-951
Offline
Yes.
systemd-networkd and NetworkManager services will fight with each other
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
thanks for the reply @ewaller . How can I know which should I remove?
Web Developer.
Arch x64 on Aspire S3-951
Offline
Which one are you using? NetworkManager provides integration with various applets so if you want to use its applets in GNOME or whatever DE you are using you likely want to disable systemd-networkd
Offline
Yeah, I'm with gnome right now.. so, systemctl disable systemd-networkd, thanks bro!
Web Developer.
Arch x64 on Aspire S3-951
Offline
That is up to you. My guess is that you will want to use NetworkManager. It seems to be the one that most of the major desktop environments like (Xfce4, KDE, Gnome). It handles most things well, but I don't care for it.
I use systemd-networkd.service (Looks for networks to which to attach and configure) along with dhcpcd.service (Obtains addresses on networks as they come up) and wpa_suplicant@.service (To manage wireless association) to control my networks and use wpa_cli and wpa_gui user space tools to control things.
NetworkManager also manages all these things pretty well, but invokes them when it needs them, and not as a systemd service but rather it spawns them itself.
Last edited by ewaller (2016-05-26 15:36:48)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
@ewaller do you have a blog entry with that information? sometimes wiki is not enough. That is the answer that I need to see the big picture, thanks!
ps: After disable systemd-networkd everything works great look my systemd-analize:
before
Startup finished in 1.824s (kernel) + 1.799s (userspace) = 3.623s
after
Startup finished in 1.814s (kernel) + 691ms (userspace) = 2.505s
Web Developer.
Arch x64 on Aspire S3-951
Offline
@ewaller do you have a blog entry with that information? sometimes wiki is not enough.
No blog, just this wiki article
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
docker.service enabled [...] systemd-networkd.service enabled
Are you using systemd-networkd for your docker containers?
I think it is possible for NetworkManager and systemd-networkd to co-exist provided they are not both attempting to manage the same interface.
I use systemd-networkd.service [...] along with dhcpcd.service
Did you know that systemd-networkd has it's own built-in dhcp client?
For my wireless & wired connections I have just systemd-networkd and wpa_supplicant enabled with the dhcp route metric set to prefer the wired connection automatically ![]()
https://wiki.archlinux.org/index.php/sy … me_machine
Last edited by Head_on_a_Stick (2016-05-26 20:17:27)
Jin, Jîyan, Azadî
Offline
Did you know that systemd-networkd has it's own built-in dhcp client?
No, I didn't. I'll check that out.
For my wireless & wired connections I have just systemd-networkd and wpa_supplicant enabled with the dhcp route metric set to prefer the wired connection automatically
That is the part I like the best. Even though my home WiFi is 'N', I love that I can start a download, walk over to my router and plug into it, watch speeds jump to 100Mb/s, and when done, disconnect and fall back to N speeds again.
Edit: I guess I did know that systemd-networkd has its own dhcp client. It turns out I did not have dhcpcd.service enabled.
Last edited by ewaller (2016-05-28 15:00:48)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Pages: 1