From: Joseph Myers <joseph@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>, <fweimer@redhat.com>,
<ashankar@redhat.com>, <ludo@gnu.org>,
<libc-alpha@sourceware.org>
Subject: Re: On the removal of nscd from Fedora, and the future of nscd.
Date: Mon, 28 Feb 2022 23:09:27 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202282305270.2276807@digraph.polyomino.org.uk> (raw)
In-Reply-To: <xnzgma7fxa.fsf@greed.delorie.com>
On Mon, 28 Feb 2022, DJ Delorie via Libc-alpha wrote:
> If we want a separate service and API for name lookups, outside of
> glibc, let's discuss. But recently we've been moving such services
> *into* glibc, to better support statically linked applications. I don't
> see an easy path forward here.
We've moved certain NSS modules such as nss_files and nss_dns into libc.
I think there is a reasonable case that all NSS modules that aren't in
libc (especially those not shipped with glibc) should be loaded only in a
separate process, not in the main process doing the name lookup, to avoid
issues with name lookup loading more or less arbitrary libraries into the
process doing the lookup.
That doesn't say what the interface should look like to any separate
process that handles doing lookup with not-in-libc NSS modules.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-02-28 23:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 20:55 Carlos O'Donell
2022-02-28 23:02 ` DJ Delorie
2022-02-28 23:09 ` Joseph Myers [this message]
2022-03-01 1:02 ` DJ Delorie
2022-03-01 9:10 ` Ludovic Courtès
2022-03-01 16:54 ` DJ Delorie
2022-03-01 17:44 ` Ludovic Courtès
2022-03-01 18:31 ` DJ Delorie
2022-03-03 13:40 ` Ludovic Courtès
2022-03-06 22:05 ` John Ericson
2022-11-20 18:34 ` Florian Klink
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=alpine.DEB.2.22.394.2202282305270.2276807@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=ashankar@redhat.com \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=ludo@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).