From: DJ Delorie <dj@redhat.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: carlos@redhat.com, ashankar@redhat.com, fweimer@redhat.com,
adhemerval.zanella@linaro.org, libc-alpha@sourceware.org
Subject: Re: On the removal of nscd from Fedora, and the future of nscd.
Date: Tue, 01 Mar 2022 13:31:05 -0500 [thread overview]
Message-ID: <xnlext7ceu.fsf@greed.delorie.com> (raw)
In-Reply-To: =?ISO-8859-1?Q?PI-LINK-24a9bc41e81bb5a7442ca440aba72ea2f7073562_(message_from_Ludovi?= =?ISO-8859-1?Q?c_Court=E8s_on_Tue, _01_Mar_2022_18:44:49_+0100)?=
Ludovic Courts <ludo@gnu.org> writes:
> Actually, by default, a Guix program on (say) Fedora-without-nscd won’t
> dlopen Fedora’s libnss_sssd.so. Instead, it’ll search in vain for
> libnss_sssd.so in its search path (which does not include /usr/lib), and
> have its name lookups fail with EAI_SYSTEM, ENOENT, or some other
> unclear error.
Ah, that's different - mostly. It still means you're using the host's
/etc/nsswitch.conf, but that just exposes a different problem - how to
handle site-wide services in isolated "programs" (flatpacks, containers,
chroots, statically linked apps, Guix).
NSCD certainly could act as that gateway, but I'd hate to rely on it
without an RFC defining the protocol, and such an RFC would enable it to
solve the problem in a wider context too.
Doing so, however, means that nscd (or some other equivalent) MUST be
present and running on all systems...
next prev parent reply other threads:[~2022-03-01 18:31 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
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 [this message]
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=xnlext7ceu.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=ashankar@redhat.com \
--cc=carlos@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).