unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 26809-done@debbugs.gnu.org
Subject: bug#26809: 08/09: services: nscd: Create /etc/resolv.conf if it does not exist.
Date: Mon, 08 May 2017 16:30:06 +0200	[thread overview]
Message-ID: <871srzmnf5.fsf@gnu.org> (raw)
In-Reply-To: <87wp9tmh7u.fsf@netris.org> (Mark H. Weaver's message of "Sun, 07 May 2017 00:19:33 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> civodul pushed a commit to branch master
>> in repository guix.
>>
>> commit 49f9d7f697d19870f01104cdb6a90a32aea87679
>> Author: Ludovic Courtès <ludo@gnu.org>
>> Date:   Tue May 2 12:21:31 2017 +0200
>>
>>     services: nscd: Create /etc/resolv.conf if it does not exist.
>>     
>>     * gnu/services/base.scm (nscd-activation): Create /etc/resolv.conf if it
>>     does not exist yet.
>
> This commit broke the boot process on my system.  The problem is that
> I'm using Network Manager, which makes /etc/resolv.conf into a symlink
> that points to /var/run/NetworkManager/resolv.conf.  Since /var/run is
> cleaned during early boot, when this new activation code runs,
> /etc/resolv.conf is a broken symlink.
>
> I guess that 'file-exists?' returns #false for a broken symlink, and the
> 'call-with-output-file' tries to open the target of the symlink, which
> fails.

Indeed.  I guess this is fixed by
c298fb133acbdc17e05a79c10ab9a9e214368264.

Thanks,
Ludo’.

      reply	other threads:[~2017-05-08 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170502103303.32490.61398@vcs0.savannah.gnu.org>
     [not found] ` <20170502103307.0229020DD6@vcs0.savannah.gnu.org>
2017-05-07  4:19   ` bug#26809: 08/09: services: nscd: Create /etc/resolv.conf if it does not exist Mark H Weaver
2017-05-08 14:30     ` 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=871srzmnf5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26809-done@debbugs.gnu.org \
    --cc=mhw@netris.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. 
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).