From: MeganerdNL <MeganerdNL@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] knot-resolver: fix configfile location in runit service
Date: Sun, 23 Jul 2023 21:37:33 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45209@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
There is a new pull request by MeganerdNL against master on the void-packages repository
https://github.com/MeganerdNL/void-packages knot-resolver-update
https://github.com/void-linux/void-packages/pull/45209
knot-resolver: fix configfile location in runit service
#### Testing the changes
- I tested the changes in this PR: **YES**
I noticed that in the default installation the default config file (/etc/knot-resolver/kresd.conf) was not read: so making changes to it, did nothing. If there is another solution to fix this properly, let me know.
A patch file from https://github.com/void-linux/void-packages/pull/45209.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-knot-resolver-update-45209.patch --]
[-- Type: text/x-diff, Size: 769 bytes --]
From 1578974a1e333f4803e88014ab1ccb4bd63baa3e Mon Sep 17 00:00:00 2001
From: MeganerdNL <meganerd@meganerd.nl>
Date: Sun, 23 Jul 2023 21:31:32 +0200
Subject: [PATCH] knot-resolver: fix configfile location in runit service
---
srcpkgs/knot-resolver/files/kresd/run | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/knot-resolver/files/kresd/run b/srcpkgs/knot-resolver/files/kresd/run
index 43b80cda27f2c..68b37b9ad67ea 100644
--- a/srcpkgs/knot-resolver/files/kresd/run
+++ b/srcpkgs/knot-resolver/files/kresd/run
@@ -2,4 +2,4 @@
exec 2>&1
[ -r ./conf ] && . ./conf
install -d -m0755 -o _knot_resolver -g _knot_resolver /run/knot-resolver
-exec kresd ${OPTS:--f 1}
+exec kresd ${OPTS:--f 1 -c ${CONF_FILE:-/etc/knot-resolver/kresd.conf}}
next reply other threads:[~2023-07-23 19:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 19:37 MeganerdNL [this message]
2023-07-23 19:42 ` classabbyamp
2023-07-23 21:00 ` MeganerdNL
2023-07-23 21:07 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-23 21:08 ` MeganerdNL
2023-07-23 21:09 ` MeganerdNL
2023-07-23 21:10 ` MeganerdNL
2023-07-23 21:10 ` MeganerdNL
2023-07-24 14:09 ` MeganerdNL
2023-07-25 6:19 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-25 6:22 ` MeganerdNL
2023-07-25 6:30 ` classabbyamp
2023-07-25 7:08 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-25 7:08 ` MeganerdNL
2023-07-25 7:08 ` MeganerdNL
2023-07-25 20:48 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-25 20:50 ` MeganerdNL
2023-07-25 20:50 ` MeganerdNL
2023-07-25 20:55 ` MeganerdNL
2023-07-25 21:08 ` [PR PATCH] [Updated] knot-resolver: config fixes + add garbage collector service MeganerdNL
2023-07-25 21:14 ` Duncaen
2023-07-26 1:28 ` classabbyamp
2023-07-26 5:22 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-26 5:25 ` MeganerdNL
2023-07-26 5:30 ` MeganerdNL
2023-07-28 4:42 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45209@inbox.vuxu.org \
--to=meganerdnl@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).