mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Jesse Hathaway <jesse@mbuki-mvuki.org>,
	musl@lists.openwall.com, Arjun Shankar <arjun@redhat.com>,
	Carlos O'Donell <carlos@redhat.com>
Subject: Re: [musl] Plans to remove nscd in Fedora
Date: Mon, 2 Nov 2020 09:50:18 -0500	[thread overview]
Message-ID: <20201102145017.GS534@brightrain.aerifal.cx> (raw)
In-Reply-To: <87zh3zg8yw.fsf@oldenburg2.str.redhat.com>

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):
> 
> <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system-level_authentication_guide/usingnscd-sssd>
> 
> SUSE also recommends disabling parts of nscd:
> 
> | -  Modify  /etc/nscd.conf
> | 
> | enable-cache   passwd    no
> | enable-cache   group      no
> 
> <https://www.suse.com/support/kb/doc/?id=000019039>
> 
> 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
https://github.com/pikhq/musl-nscd (not part of musl, but by a
long-time contributor) would be a useful basis for building a
replacement glibc systems could use too?

Rich

  reply	other threads:[~2020-11-02 14:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1924902939.18027073.1603105167534.JavaMail.zimbra@redhat.com>
2020-10-19 11:13 ` Arjun Shankar
2020-10-20  1:08   ` Rich Felker
2020-10-23 11:35     ` Florian Weimer
2020-10-23 12:01       ` Tim Tassonis
2020-10-23 12:09         ` Florian Weimer
2020-10-23 13:29     ` Carlos O'Donell
2020-10-23 13:37       ` Laurent Bercot
2020-10-23 14:14       ` Jesse Hathaway
2020-10-23 16:58         ` Rich Felker
2020-10-26 12:20         ` Florian Weimer
2020-10-26 13:12           ` Rich Felker
2020-11-02 13:54             ` Florian Weimer
2020-11-02 14:50               ` Rich Felker [this message]
2020-11-03  9:07                 ` Florian Weimer
2020-11-03 15:41                   ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201102145017.GS534@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=arjun@redhat.com \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=jesse@mbuki-mvuki.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).