From: Eric Leblond <eric@regit.org>
To: Kaarle Ritvanen <kaarle.ritvanen@datakunkku.fi>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH ulogd2 1/2] ulogd.conf: harmonize log file options with module default values
Date: Tue, 07 Mar 2017 16:00:02 +0200 [thread overview]
Message-ID: <1488895202.4890.4.camel@regit.org> (raw)
In-Reply-To: <20170213094729.23478-1-kaarle.ritvanen@datakunkku.fi>
Hello Kaarle,
Thanks for the cleaning work. Some comment inside.
On Mon, 2017-02-13 at 11:47 +0200, Kaarle Ritvanen wrote:
> Signed-off-by: Kaarle Ritvanen <kaarle.ritvanen@datakunkku.fi>
> ---
> ulogd.conf.in | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/ulogd.conf.in b/ulogd.conf.in
> index 2fcf39a..6e7bdf4 100644
> --- a/ulogd.conf.in
> +++ b/ulogd.conf.in
> @@ -183,15 +183,15 @@ nlgroup=1
> socket_path="/tmp/nuauth_ulogd2.sock"
>
> [emu1]
> -file="/var/log/ulogd_syslogemu.log"
> +file="/var/log/ulogd.syslogemu"
I really like the idea of getting an harmonized naming for the log
files but I think we should do it reverse for values that are not
commented in the configuration file. Most distributions and install are
shipping with a copy of default configuration.
Most users won't have changed the values that are uncommented. So they
will have on disk the log file with name defined in the configuration
file. And they will benefit from a new logrotate file. Thus we should
use the file name defined in the conf as value of the default file name
in code.
Could you resubmit a patchset ?
BR,
--
Eric Leblond <eric@regit.org>
Blog: https://home.regit.org/
next prev parent reply other threads:[~2017-03-07 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 9:47 [PATCH ulogd2 1/2] ulogd.conf: harmonize log file options with module default values Kaarle Ritvanen
2017-02-13 9:47 ` [PATCH ulogd2 2/2] rotate all default output files Kaarle Ritvanen
2017-03-07 14:00 ` Eric Leblond [this message]
2017-04-12 11:40 ` [PATCH ulogd2 1/2] ulogd.conf: harmonize log file options with module default values Kaarle Ritvanen
2017-05-15 22:05 ` Eric Leblond
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=1488895202.4890.4.camel@regit.org \
--to=eric@regit.org \
--cc=kaarle.ritvanen@datakunkku.fi \
--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 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).