unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: adriano <randomlooser@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: nscd
Date: Tue, 01 Feb 2022 14:28:55 +0100	[thread overview]
Message-ID: <87h79i90kp.fsf@elephly.net> (raw)
In-Reply-To: <50cb3d7431901bdb0a5bdd279a8e3c5e6ffe2cb7.camel@riseup.net>


adriano <randomlooser@riseup.net> writes:

> Il giorno lun, 31/01/2022 alle 23.30 +0100, Ricardo Wurmus ha scritto:
>> 
>> adriano <randomlooser@riseup.net> writes:
>> 
>> > The "Application Setup" in the manual
>> > ( https://guix.gnu.org/manual/en/html_node/Application-Setup.html )
>> > suggests to run the nscd service
>> > 
>> > "we strongly recommend that the system run the GNU C library’s name
>> > service cache daemon, nscd, which should be listening on the
>> > /var/run/nscd/socket socket."
>> > 
>> >  found such service already running on my Ubuntu installation and
>> > the
>> > mentioned socket is there
>> > 
>> > But now I'm wondering: does the manual refer to the host distro
>> > when it
>> > says "the system" ?
>> 
>> Yes.
>> 
>> The reason is that nscd communicates with processes over a network
>> protocol, which allows binaries built with Guix to talk to user
>> account
>> services on a foreign distro.  Alternative account services require
>> loading of binary plugins, which would not be possible when these
>> plugins are linked with incompatible libraries.
>> 
>
> Thank you, Ricardo
>
> so because the nscd service being used is provided by the Ubuntu host,
> the issue I'm running into (discussed in another thread) is not due to
> the wrong nscd service being used
>
> am I right ?

Correct.  It should not be related to nscd.

nscd from Ubuntu should work just fine because the protocol is the same
no matter if client and server are linked with different libraries.

-- 
Ricardo


      reply	other threads:[~2022-02-01 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 20:41 nscd adriano
2022-01-31 22:30 ` nscd Ricardo Wurmus
2022-02-01 10:32   ` nscd adriano
2022-02-01 13:28     ` Ricardo Wurmus [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=87h79i90kp.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=randomlooser@riseup.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).