From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org, alexandre@r42.ch
Subject: Re: [PATCH nft v2] main: display errors through stderr
Date: Tue, 24 Feb 2015 20:01:40 +0100 [thread overview]
Message-ID: <20150224190140.GA32754@salvia> (raw)
In-Reply-To: <20150224183505.GN3713@acer.localdomain>
On Tue, Feb 24, 2015 at 06:35:05PM +0000, Patrick McHardy wrote:
> On 24.02, Pablo Neira Ayuso wrote:
> > Debugging still goes through stdout as Patrick requests.
> >
> > Closes: https://bugzilla.netfilter.org/show_bug.cgi?id=1000
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
>
> Thinking about it, EREC_INFORMATIONAL should also go to stdout I
> suppose. But since we don't have any of those yet, we can change
> it once we get the first message of this type.
I just remembered that bison is currently using stderr as output for
debugging.
We're also telling people to save their rulesets via:
nft list ruleset > file
If debugging still goes to stdout this will cause them problems. Not
sure yet we should use stdout for debugging.
next prev parent reply other threads:[~2015-02-24 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 18:32 [PATCH nft v2] main: display errors through stderr Pablo Neira Ayuso
2015-02-24 18:35 ` Patrick McHardy
2015-02-24 19:01 ` Pablo Neira Ayuso [this message]
2015-02-24 19:18 ` Patrick McHardy
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=20150224190140.GA32754@salvia \
--to=pablo@netfilter.org \
--cc=alexandre@r42.ch \
--cc=kaber@trash.net \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.