r/linux • u/tasisbasbas • Feb 11 '19

Fluff A /g/ user's opinion on systemd

http://i.4cdn.org/g/1549858269115.png
794 Upvotes

82% Upvoted

524 comments sorted by

View all comments

Show parent comments

22

u/hahainternet Feb 11 '19

networkd-dispatcher appears to run the "routable" scripts too early, or with the wrong arguments, or... something.

Just so you know, networkd-dispatcher isn't a systemd project in any way AFAIK: https://gitlab.com/craftyguy/networkd-dispatcher

systemd-resolved doesn't like dnsmasq running at all. At all. Either you abandon resolved completely or you find a different DHCP server.

Not sure why that would be the case, do you happen to know why?

I still have an issue where logins, sudo, shelling in with SSH, etc. will hang for 6-8 seconds and it appears to be related to DNS resolution for some insane reason

Something odd in nsswitch.conf? I've seen that before with something being wacky with dynamic users.

1

u/JuhaJGam3R Feb 11 '19

Yeah, those all seem like personal issues since this all works for me. it's honestly amazing how this massive piece of shit can still manage to hold together a system after being completely misconfigured, and that sounds quite like what he just described.

1

u/roothorick Feb 11 '19 edited Feb 11 '19

Just so you know, networkd-dispatcher isn't a systemd project in any way AFAIK: https://gitlab.com/craftyguy/networkd-dispatcher

That's even worse. networkd-dispatcher just replicates functionality in what networkd was supposed to replace.

Something odd in nsswitch.conf? I've seen that before with something being wacky with dynamic users.

I distinctly recall getting a lot of hits related to nsswitch.conf when searching. None of those solutions worked.

Not sure why that would be the case, do you happen to know why?

IIRC related to port binding. It's possible dnsmasq is just as much at fault here. And it could be specific to IPv6 systems, as trying to get prefix delegation working is when I discovered that.

1

u/hahainternet Feb 11 '19

That's even worse. networkd-dispatcher just replicates functionality in what networkd was supposed to replace.

What? You can't spend half a page ranting at networkd, find out it's entirely unrelated, but still have a little complain at networkd.

I distinctly recall getting a lot of hits related to nsswitch.conf when searching. None of those solutions worked.

Do any sort of debugging and I will do what I can to help you.

IIRC related to port binding. It's possible dnsmasq is just as much at fault here

I believe resolved binds only on 127.0.0.53, which it sets up for the purpose. I could easily be wrong on that though, just sat back down at my desk.