From: Christopher Batten <cbatten@cornell.edu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: "user with UID not found" error
Date: Wed, 27 Jul 2022 19:50:07 +0000 [thread overview]
Message-ID: <578194AB-E4D5-4A72-B974-5EE63A0CB422@cornell.edu> (raw)
In-Reply-To: <87h732radc.fsf@elephly.net>
Hmmm ... this made me think that running both was not a great idea?
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system-level_authentication_guide/usingnscd-sssd
But I am not an expert on any of this :) I guess the key is to just make sure you only enable caching for hosts in /etc/nscd.conf?
Best,
Chris
> On Jul 27, 2022, at 8:44 AM, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Hi Christopher,
>
>> Turns out we are using SSSD not NCSD on our Linux systems. It seems to be working fine:
>
> You will need to run NSCD if you want Guix software to be able to talk
> to the system’s SSSD. The reason is that SSSD works by having
> applications load a library whereas NSCD implements a network protocol.
> Software built with Guix cannot load the system libary due to ABI
> conflict, but it *can* talk to NSCD over the network.
>
> The system NSCD talks to the system SSSD, so there’s no problem there.
>
> --
> Ricardo
next prev parent reply other threads:[~2022-07-27 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 17:56 "user with UID not found" error Christopher Batten
2022-07-22 19:25 ` Ricardo Wurmus
2022-07-26 21:01 ` Christopher Batten
2022-07-27 12:44 ` Ricardo Wurmus
2022-07-27 19:50 ` Christopher Batten [this message]
2022-07-29 1:14 ` Chris Marusich
2022-08-01 16:16 ` Christopher Batten
2022-08-01 18:37 ` Jack Hill
2022-08-01 19:49 ` Ricardo Wurmus
2022-08-02 17:48 ` Christopher Batten
2022-08-02 18:17 ` Ricardo Wurmus
2022-08-02 18:24 ` Christopher Batten
2022-08-02 20:53 ` Ricardo Wurmus
2022-08-03 19:26 ` Christopher Batten
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=578194AB-E4D5-4A72-B974-5EE63A0CB422@cornell.edu \
--to=cbatten@cornell.edu \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.