From mboxrd@z Thu Jan  1 00:00:00 1970
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: NetworkManager instead of Wicd in =?utf-8?Q?=E2=80=98%desktop?=
	=?utf-8?Q?-services=E2=80=99=3F?=
Date: Wed, 02 Aug 2017 09:25:45 -0400
Message-ID: <87r2wut82u.fsf@gmail.com>
References: <87iniaf06l.fsf@gnu.org> <87bmo1ltus.fsf@netris.org>
	<87zibk7ptz.fsf@gmail.com> <87379c7n5q.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38131)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <maxim.cournoyer@gmail.com>) id 1dcteq-0001fp-8B
	for guix-devel@gnu.org; Wed, 02 Aug 2017 09:25:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <maxim.cournoyer@gmail.com>) id 1dctem-0007Lw-9L
	for guix-devel@gnu.org; Wed, 02 Aug 2017 09:25:52 -0400
In-Reply-To: <87379c7n5q.fsf@gnu.org> ("Ludovic
	\=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\=
	\=\?utf-8\?Q\?s\?\= message of "Mon, 31 Jul 2017 15:26:25 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>

ludo@gnu.org (Ludovic Court=C3=A8s) writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> I've noticed the same (lack of DNS resolution) following a reboot for
>> some minutes and was also wondering what was causing this. I'm using
>> wicd as part of the %desktop-services, so that specific problem is
>> probably not related to NetworkManager.
>
> Our default nscd config caches lookup failures for 20 seconds by default
> (see =E2=80=98nscd-cache=E2=80=99 in the manual.)  So if you look up a ho=
st before
> networking is up, and it fails, then there=E2=80=99s a window during which
> lookup will keep failing.
>
> I don=E2=80=99t know if that explains what you=E2=80=99re seeing.

It can take much longer than 20 s upon a reboot to have the name
resolution working again (more than 5 minutes), so that doesn't seem to
explain it by itself.