3 ms·
GAI just needs to go. It needs to be moved to its own daemon with a simple RPC. libc is kinda schizophrenic in this regard. It has mostly obviously low-level f
by cyberax 3y ago
GAI just needs to go. It needs to be moved to its own daemon with a simple RPC.
libc is kinda schizophrenic in this regard. It has mostly obviously low-level functions like string manipulation and memory management, and then unexpectedly a DNS client implementation and a support for arbitrary runtime plugins (for PAM).
- deleted 3y ago[deleted]
- tadfisher 3y agoThis, along with the general inability to handle per-interface DNS resolution, is the primary reason systemd-resolved exists.
- xerxes901 3y agoThis is essentially what systemd-resolved with the nss-resolve NSS module is right? It’s possible to use /etc/nsswitch.conf to entirely disable the built-in DNS resolution in glibc if you want.
- alexgartrell 3y agoIME, familiarity with /etc/nsswitch.conf and the rest of the nss stuff is very highly correlated with people who have seen some shit.
- cyberax 3y agoYep, it's close. But you still depend on the unholy mess that is nsswitch.conf It's still a bit worrying, with manual JSON parsing: https://github.com/systemd/systemd/blob/79f487038444646f5bce1f5a18d51cda5f20b268/src/nss-resolve/nss-resolve.c#L598 https://github.com/systemd/systemd/blob/79f487038444646f5bce... But at least it's just ~600 lines of fairly straightforward code. You also can get most of it with nscd. (Sigh, I wish BUS1 guys pushed their project to completion)