unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josua Stingelin <josuast@hotmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: unbound-service-type
Date: Sun, 20 Feb 2022 18:06:01 +0100	[thread overview]
Message-ID: <DB9PR06MB7657941D845808925CD589F7AA399@DB9PR06MB7657.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <87leydqg53.fsf@gnu.org>

Hi Ludo,

Thank you for your reply!

> I’d recommend passing the config file directly, as in:
> 
>   "-c" #$(local-file "unbound.conf")

Doing that now.

> > However when I add these to my operating-system configuration, and copy the
> > configuration file using the etc-service-type it doesn't run on start.
> 
> Do you have additional info as to why it doesn’t start?  Perhaps error
> messages in /var/log/messages or something?

Turns out unbound segfaults when chrooting to a read-only directory. And if one
doesn't explicitly turn off the chroot it tries to chroot to 
"<binary directory>/../etc" (or something similar).

  unbound[1407]: segfault at ffffffffffffffb8 ip 00007fd6498ecd67 sp 00007fffa4366550 error 5 in libc-2.33.so[7fd64984f000+141000]


Should I report this upstream - or is this considered a configuration issue?


I've gotten the service up and running. Going to try and generate the
configuration file based on the scheme configuration next.


Thank you for your help and sorry for posting pre-maturely. I suppose searching
a bit longer would have gotten me on track anyway.

Kind Regards,


      reply	other threads:[~2022-02-20 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 11:42 unbound-service-type Josua Stingelin
2022-02-12  3:43 ` unbound-service-type jbranso
2022-02-14 21:42 ` unbound-service-type Ludovic Courtès
2022-02-20 17:06   ` Josua Stingelin [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=DB9PR06MB7657941D845808925CD589F7AA399@DB9PR06MB7657.eurprd06.prod.outlook.com \
    --to=josuast@hotmail.com \
    --cc=guix-devel@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.
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).