unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Dealing with foreign distros without nscd
Date: Sat, 29 Aug 2020 12:07:50 +0200	[thread overview]
Message-ID: <87wo1hlq89.fsf@gnu.org> (raw)
In-Reply-To: <87wo1jnl2u.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 28 Aug 2020 12:03:53 +0200")

Hi!

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>
>> The workaround I found is to add ‘sssd’ to the pack, like so:
>>
>>   guix pack -RR -S /lib=lib -S /bin=bin sssd guile
>>
>> That way, on the other machine, you can set LD_LIBRARY_PATH such that
>> Guix’ libnss_sss.so gets loaded:
>>
>>   tar xf /path/to/pack.tgz
>>   LD_LIBRARY_PATH=$PWD/lib ./bin/guile -c '(pk (getpw (getuid)))'
>>
>> It works!  However, if people have ideas of less arcane workarounds, I’m
>> interested.
>
> Interesting!  I wonder if this really is a general solution or if it
> only works under special circumstances (like the cluster node using sssd
> already).  Will, for example, accounts that are managed via Active
> Directory / LDAP be visible if all we do is preload the Guix sssd
> libraries?

In general, you have to put the modules /etc/nsswitch.conf refers to in
$LD_LIBRARY_PATH.  The example above works for ‘sss’ but you would do
something similar for ‘mdns’, ‘ldap’, or whatever.

It’s clunky because you have to know beforehand, when you make the pack,
what nsswitch.conf requires.

Ludo’.


      reply	other threads:[~2020-08-29 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28  9:38 Dealing with foreign distros without nscd Ludovic Courtès
2020-08-28 10:03 ` Ricardo Wurmus
2020-08-29 10:07   ` Ludovic Courtès [this message]

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=87wo1hlq89.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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