From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: (Not technically a bug, yet very counter-intuitive and prone to breakage) Runit nftables service imports "/etc/nftables.conf" instead of the more sensible "/etc/nftables/nftables.conf"
Date: Thu, 15 Dec 2022 11:06:19 +0100 [thread overview]
Message-ID: <20221215100619.6VK3J6yonVKNFvlBLc_Q7GNE_UasYCazyr9EUUL3WvI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41100@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/41100#issuecomment-1352827556
Comment:
Arch also uses /etc/nftables.conf, so I am not sure what's the issue. The service was clearly failing to start and reading the service file or the handbook section would uncover you are using the wrong path.
prev parent reply other threads:[~2022-12-15 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 0:32 [ISSUE] " TeusLollo
2022-12-15 6:56 ` paper42
2022-12-15 7:47 ` paper42
2022-12-15 9:57 ` [ISSUE] [CLOSED] " TeusLollo
2022-12-15 9:57 ` TeusLollo
2022-12-15 10:06 ` [ISSUE] [CLOSED] " paper42
2022-12-15 10:06 ` paper42 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221215100619.6VK3J6yonVKNFvlBLc_Q7GNE_UasYCazyr9EUUL3WvI@z \
--to=paper42@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).