3 ms·
> One solution might be if the statically-linked program included an nscd client, since most people using NSS+LDAP will be using nscd for caching. No, that's n
by JoshTriplett 11y ago
> One solution might be if the statically-linked program included an nscd client, since most people using NSS+LDAP will be using nscd for caching.
No, that's not OK either; many people use other NSS modules, including mdns (for .local names), resolve (for local resolved support), resolving "localhost" (via "myhostname"), and resolving local container hostnames.
If you want to resolve any of the things NSS supports, use NSS.
- skissane 11y agoWhy can't nscd support those other NSS modules too? (Even if it doesn't work with them at present, could it not be extended to do so?) Rather than having NSS plugins loaded into every process which needs name services, why not centralise all name services in a daemon (whether nscd or sssd or something else)? Then client processes don't need to actually load the NSS code into their own address space, they can just speak a simple protocol over IPC to access this functionality out-of-process.
- justincormack 11y agoAndroid does something much like that I believe.