Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 2 Nov 2020 09:50:18 -0500
From: Rich Felker <>
To: Florian Weimer <>
Cc: Jesse Hathaway <>,,
	Arjun Shankar <>,
	Carlos O'Donell <>
Subject: Re: Plans to remove nscd in Fedora

On Mon, Nov 02, 2020 at 02:54:31PM +0100, Florian Weimer wrote:
> * Rich Felker:
> > It's not mandatory on glibc, but it's a widely deployed existing
> > interface on most "big" systems, and it's easy to add with a quick
> > apt-get or whatever on others if you find you need it for integration
> > with non-glibc binaries.
> This has not been true for quite a few years because using nscd along
> with sssd for the same databases is not supported (sssd is where all the
> domain integration work happens these days):
> <>
> SUSE also recommends disabling parts of nscd:
> | -  Modify  /etc/nscd.conf
> | 
> | enable-cache   passwd    no
> | enable-cache   group      no
> <>
> I think SUSE has largely switched to SSSD as well for the most recent
> product releases, but I do not have much insight into their work
> unfortunately.
> > If it remains easy to add, having it not installed by default is
> > really not a big deal,
> (we have been in this situation for many, many years)
> > but I kinda worry about bitrot/breakage from suddenly having far fewer
> > users.
> nscd is already very broken and has issues with workloads that trigger
> many cache misses.

Thanks for filling me in on the status of this. Perhaps (not part of musl, but by a
long-time contributor) would be a useful basis for building a
replacement glibc systems could use too?


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.