All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo@debian.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [conntrack-tools PATCH 1/3] log: introduce a mechanism to know if log was initialized
Date: Wed, 9 Nov 2016 00:30:04 +0100	[thread overview]
Message-ID: <20161108233004.GA10359@salvia> (raw)
In-Reply-To: <147825582201.31164.6123720868667079634.stgit@nfdev2.cica.es>

On Fri, Nov 04, 2016 at 11:37:02AM +0100, Arturo Borrero Gonzalez wrote:
> This will allow to call dlog() function from all the points in the
> execution at runtime.
> 
> If the log was not initialized, then we just fprintf and return.
> 
> By now, we can't init the log engine earlier because we require config
> from the user, so there is a egg-chicken problem.
> This means that we can't log parsing messages to logfiles but only to
> stderr/stdout.

Series applied, thanks Arturo.

A couple of things that would be good to revisit, just for the record:

1) Get rid of deprecated stuff. By digging into the git log history I
   guess you can probably find that they have been deprecated since
   ~2008, so it's been already enough time for people to update
   configuration files.

2) Make sure the configuration parser works fine with defaults, I mean
   with the bare minimum configuration. I remember reports from people
   that wrote configuration files from scratch, that were not working.
   So I pointed them to the example files to use as template.

Thanks.

      parent reply	other threads:[~2016-11-08 23:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 10:37 [conntrack-tools PATCH 1/3] log: introduce a mechanism to know if log was initialized Arturo Borrero Gonzalez
2016-11-04 10:37 ` [conntrack-tools PATCH 2/3] conntrackd: replace error reporting in the config parser with dlog() Arturo Borrero Gonzalez
2016-11-04 10:37 ` [conntrack-tools PATCH 3/3] conntrackd: replace fprintf calls " Arturo Borrero Gonzalez
2016-11-08 23:30 ` 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=20161108233004.GA10359@salvia \
    --to=pablo@netfilter.org \
    --cc=arturo@debian.org \
    --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.