From: "Caleb Herbert" <csh@bluehome.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Application Setup on Trisquel
Date: Tue, 24 Oct 2017 16:33:00 -0700 (PDT) [thread overview]
Message-ID: <1508887980.7490@bluehome.net> (raw)
In-Reply-To: <873768nt5e.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]
Ludovic Courtès <ludo@gnu.org> wrote ..
> You should get nscd from Trisquel, in its ‘nscd’ package. You’ll have
> more success asking Trisquel questions on Trisquel fora though. :-)
Done.
> > * How do I make sure ncsd is "listening on the /var/run/nscd/socket
> > socket"?
>
> You could run “lsof | grep nscd”, but it’s likely to be the case once
> nscd running.
It seems to be running. :-)
root@leela:~# lsof | grep nscd | grep '\/var\/run\/'
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
/run/user/1000/gvfs
Output information may be incomplete.
nscd 2691 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2692 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2693 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2694 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2695 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2697 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2698 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2699 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2700 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
nscd 2691 2701 root 12u unix 0xffff8800361d4000
0t0 404213 /var/run/nscd/socket
> > The manual instructs users on foreign distros to export environment
> > variables. Doing this in the shell makes the changes temporary.
> > Where should these changes be made permanent? (It is bad practice to
> > put environment variables in .bashrc.)
>
> /etc/profile would be the right place.
Is this correct?
# echo 'export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale' >>/etc/p
rofile
# echo 'export SSL_CERT_DIR="$HOME/.guix-profile/etc/ssl/certs"' >>/
etc/profile
# echo 'export SSL_CERT_FILE="$HOME/.guix-profile/etc/ssl/certs/ca-c
ertificates.crt"' >>/etc/profile
# echo 'export GIT_SSL_CAINFO="$SSL_CERT_FILE"' >>/etc/profile
# echo 'export CURL_CA_BUNDLE="$HOME/.guix-profile/etc/ssl/certs/ca-
certificates.crt"' >>/etc/profile
# echo 'source $HOME/.guix-profile/etc/profile' >>/etc/profile
next prev parent reply other threads:[~2017-10-24 23:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 18:12 Application Setup on Trisquel Caleb Herbert
2017-10-24 21:16 ` Ludovic Courtès
2017-10-24 22:04 ` Caleb Herbert
2017-10-26 17:54 ` Ludovic Courtès
2017-10-27 1:02 ` Chris Marusich
2017-10-24 23:33 ` Caleb Herbert [this message]
2017-10-24 23:44 ` Caleb Herbert
2017-10-26 17:52 ` Ludovic Courtès
2017-10-26 20:05 ` Caleb Herbert
2017-10-25 0:36 ` Mikhail Kryshen
2017-10-26 17:53 ` Ludovic Courtès
2017-10-27 3:29 ` Caleb Herbert
2017-11-08 6:39 ` Caleb Herbert
2017-11-09 21:05 ` Chris Marusich
2017-11-10 21:29 ` Caleb Herbert
2017-11-12 14:55 ` Adonay Felipe Nogueira
2017-11-12 17:09 ` Adonay Felipe Nogueira
2017-11-12 13:02 ` Adonay Felipe Nogueira
2017-11-02 2:59 ` Mark H Weaver
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=1508887980.7490@bluehome.net \
--to=csh@bluehome.net \
--cc=help-guix@gnu.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).