From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Martin Gignac <martin.gignac@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: 'Did not kill' written out when redirecting 'nft list ruleset' in 0.9.8
Date: Thu, 25 Feb 2021 00:37:31 +0100 [thread overview]
Message-ID: <20210224233731.GA16083@salvia> (raw)
In-Reply-To: <CANf9dFOxZ9VyjyruHuU3OJu0+-1-Bsnhaw2u8XfqyDpmK26mRg@mail.gmail.com>
On Wed, Feb 24, 2021 at 06:00:23PM -0500, Martin Gignac wrote:
> Hi,
>
> With nft 0.9.8, if I run 'nft list ruleset' and redirect to a file, it
> prints out "Did not kill":
>
> [root@s116r2l1fw01b magi]# nft -v
> nftables v0.9.8 (E.D.S.)
> [root@s116r2l1fw01b magi]# nft list ruleset > /dev/null
> Did not kill
> [root@s116r2l1fw01b magi]#
>
> On 0.9.7, it does not:
>
> [root@s116r2l1fw01b magi]# nft -v
> nftables v0.9.7 (Anyface)
> [root@s116r2l1fw01b magi]# nft list ruleset > /dev/null
> [root@s116r2l1fw01b magi]#
>
> Does anyone else see this behavior? If so, do you know what "Did not
> kill" is/means?
Looks like stderr debugging slipped through master, it's already fixed in:
533565244d88 ("payload: check icmp dependency before removing previous icmp expression")
prev parent reply other threads:[~2021-02-24 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 23:00 'Did not kill' written out when redirecting 'nft list ruleset' in 0.9.8 Martin Gignac
2021-02-24 23:37 ` Pablo Neira Ayuso [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=20210224233731.GA16083@salvia \
--to=pablo@netfilter.org \
--cc=martin.gignac@gmail.com \
--cc=netfilter@vger.kernel.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