Opened 14 months ago
Closed 14 months ago
#5349 closed enhancement (fixed)
glibc: Do not build nscd anymore
| Reported by: | Xi Ruoyao | Owned by: | lfs-book |
|---|---|---|---|
| Priority: | normal | Milestone: | 12.1 |
| Component: | Book | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description
In SysV revision, we don't provide a bootscript of nscd, so it's essentially useless.
In Systemd revision, nscd is enabled by default (with systemctl preset-all) but it does not work correctly in my IPv4+IPv6 network environment: it often only caches an IPv4 address of a host name, then the system will never resolve this host to IPv6. And systemd-resolved already caches the address of hosts much better than nscd does. Thus I always stop and disable nscd.service once I boot LFS Systemd.
Fedora has also removed nscd in 2022: https://fedoraproject.org/wiki/Changes/RemoveNSCD
We can pass --disable-nscd to Glibc configure and remove the commands to install nscd support files & systemd units.
Change History (3)
comment:1 by , 14 months ago
comment:2 by , 14 months ago
We can say "Do not build the name service cache daemon. It has some bugs which are hard to fix and the Glibc developers don't want to pay much efforts to fix them."
DNS caching is handled by systemd-resolved or unbound. The caching for LDAP etc. are handled by sssd in mainstream distros but we don't have it in BLFS.
comment:3 by , 14 months ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed at commit 25b3c0f7209a18714be7489b84bbd0b4d20ee4ae
This seems like a reasonable thing to do, but I am unsure how to word the explanation. Perhaps "Do not build the obsolete nscd daemon." ??
The equivalent caching is done by systemd but not by sysV. Wouldn't the unbound package in BLFS provide the same capability for network data and ldap for distributed data?