From: bobertlo <bobertlo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [wip] new package: firewalld-1.0.2
Date: Tue, 14 Dec 2021 04:55:31 +0100 [thread overview]
Message-ID: <20211214035531.XqNk8ODyFzSKW-Nh2PU3qPaSvRJIwYb-B8amEnF9zus@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34378@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
New comment by bobertlo on void-packages repository
https://github.com/void-linux/void-packages/pull/34378#issuecomment-993127606
Comment:
> What kind of output does `firewalld` produce? If there is useful output, you might want to skip redirecting to the bit bucket and add a log service (see, _e.g._, the service provided by `duiadns`) to capture the text.
When you enable rejection logging that happens through the kernel logs. The only output from firewalld is like:
```
Starting firewalld - dynamic firewall daemon....
Started firewalld - dynamic firewall daemon.
```
Plus some warnings if backends are not available (the nftables backend alone is enough for it to work though)
EDIT: I'm not really familiar with runit logging conventions. Should I not redirect the output and let it display on the console?
EDIT: I see the vlogger setup. Would it be normal to spawn a log collector in this case on void?
next prev parent reply other threads:[~2021-12-14 3:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 7:12 [PR PATCH] [wip] new package: firewalld-1.0.1 bobertlo
2021-12-04 7:19 ` [PR PATCH] [Updated] " bobertlo
2021-12-04 8:17 ` bobertlo
2021-12-04 8:23 ` bobertlo
2021-12-04 8:24 ` bobertlo
2021-12-07 4:53 ` [PR PATCH] [Updated] [wip] new package: firewalld-1.0.2 bobertlo
2021-12-13 13:18 ` [PR REVIEW] " ahesford
2021-12-14 2:05 ` [PR PATCH] [Updated] " bobertlo
2021-12-14 2:06 ` bobertlo
2021-12-14 3:40 ` bobertlo
2021-12-14 3:42 ` bobertlo
2021-12-14 3:55 ` bobertlo [this message]
2021-12-14 3:56 ` bobertlo
2021-12-14 4:48 ` [PR PATCH] [Updated] " bobertlo
2021-12-15 0:24 ` bobertlo
2021-12-15 14:01 ` bobertlo
2021-12-16 0:05 ` [PR REVIEW] " paper42
2021-12-16 0:05 ` paper42
2021-12-16 0:05 ` paper42
2021-12-16 1:45 ` [PR PATCH] [Updated] " bobertlo
2021-12-16 10:53 ` [PR REVIEW] " paper42
2021-12-16 10:53 ` paper42
2021-12-16 13:20 ` [PR PATCH] [Updated] " bobertlo
2022-02-07 20:59 ` bobertlo
2022-02-07 20:59 ` [PR PATCH] [Closed]: " bobertlo
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=20211214035531.XqNk8ODyFzSKW-Nh2PU3qPaSvRJIwYb-B8amEnF9zus@z \
--to=bobertlo@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).