all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Florian Paul Schmidt <mista.tapas@gmx.net>
To: "Ludovic Courtès" <ludo@gnu.org>, "Ricardo Wurmus" <rekado@elephly.net>
Cc: 22209@debbugs.gnu.org
Subject: bug#22209: name resolution failures in installer image
Date: Sun, 20 Dec 2015 11:12:32 +0100	[thread overview]
Message-ID: <56767F10.40202@gmx.net> (raw)
In-Reply-To: <87a8p6xqcj.fsf@gnu.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 19.12.2015 19:09, Ludovic Courtès wrote:

> However, nscd is reportedly behaving strangely: 
> <http://bugs.gnu.org/20816>.
> 
> Do you initially get successful lookups for hydra.gnu.org, and 
> eventually lookup failures?

Yes, that's at least in my case precisely what happens. It works for
the first few packages during system init, and then at some point in
time fails.

I'll try to reproduce and then restart the nscd to see if it helps
(when I find time to do it)..

Flo


- -- 
https://fps.io
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWdn8QAAoJEA5f4Coltk8ZrSIH/3YKmBO2ZDCqxxZGWYJDRgQc
Q74OFkSrw56ov29uSU+Xs63njem19PLxyECLoICex2tOMOuELpowKt0ee8hS/7PT
eYyRlMiUfIk4WC2qpFGQtfURDOmsAiWCGP2LzBO1RqhgU5CtgnChH5Z7ZVmlNloy
EqVKZ0tpquagf1k6FkMsk65fY6gPa2D+2Ova1SkwtEiIRwMDMNkguadHXu9LShKu
9fSOnP7BXwAZfPC6hPyrB8tjUWtr8PUlzYNsLsW6PTqtRNry5QSSa2I4wsx9Gjse
HQ3NeRjp3RPvOx/LwP5+nGaTsUN8R8aPSX3eMumpBfzrImLqANExhcOvkFtkL6U=
=R54m
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-12-20 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19  8:04 bug#22209: name resolution failures in installer image Florian Paul Schmidt
2015-12-19  8:45 ` Leo Famulari
2015-12-19 10:25   ` Ricardo Wurmus
2015-12-19 18:09     ` Ludovic Courtès
2015-12-20 10:12       ` Florian Paul Schmidt [this message]
2016-02-10 20:54       ` Ludovic Courtès
2016-05-03 20:26         ` Ludovic Courtès

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=56767F10.40202@gmx.net \
    --to=mista.tapas@gmx.net \
    --cc=22209@debbugs.gnu.org \
    --cc=ludo@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.