unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Christopher Batten <cbatten@cornell.edu>
Cc: Ricardo Wurmus <rekado@elephly.net>,
	"help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: "user with UID not found" error
Date: Thu, 28 Jul 2022 18:14:44 -0700	[thread overview]
Message-ID: <CAEKzfHk1Tf5HjhznYVU3y+5bwCLW8h=Mwkc9hTd-4mbKH37G8g@mail.gmail.com> (raw)
In-Reply-To: <578194AB-E4D5-4A72-B974-5EE63A0CB422@cornell.edu>

FYI: https://lists.gnu.org/archive/html/guix-devel/2022-02/msg00263.html

Sorry for the top post; I'm not on my usual computer.

On Wed, Jul 27, 2022 at 12:51 PM Christopher Batten <cbatten@cornell.edu>
wrote:

>
> 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
>
>

  reply	other threads:[~2022-07-29  1:41 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
2022-07-29  1:14         ` Chris Marusich [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to='CAEKzfHk1Tf5HjhznYVU3y+5bwCLW8h=Mwkc9hTd-4mbKH37G8g@mail.gmail.com' \
    --to=cmmarusich@gmail.com \
    --cc=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.
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).