From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>
Subject: Re: [conntrackd PATCH v3] conntrackd: add systemd support
Date: Fri, 13 Nov 2015 16:54:31 +0100 [thread overview]
Message-ID: <20151113155431.GA1353@salvia> (raw)
In-Reply-To: <CAOkSjBim_sssQko+JedaZaa1w=SPVhYKBPvFKW7hGmCFFKXw5A@mail.gmail.com>
On Fri, Nov 13, 2015 at 12:39:22PM +0100, Arturo Borrero Gonzalez wrote:
> On 13 November 2015 at 11:59, Arturo Borrero Gonzalez
> <arturo.borrero.glez@gmail.com> wrote:
> > diff --git a/doc/stats/conntrackd.conf b/doc/stats/conntrackd.conf
> > index 16d7a80..b1cca07 100644
> > --- a/doc/stats/conntrackd.conf
> > +++ b/doc/stats/conntrackd.conf
> > @@ -3,6 +3,14 @@
> > #
> > General {
> > #
> > + # Enable systemd support. If conntrackd is compiled with the proper
> > + # configuration, you can use a systemd service unit of Type=notify
> > + # and use conntrackd with systemd watchdog as well.
> > + # Default is: on
> > + #
> > + #Systemd off
> > +
> > + #
> > # Set the nice value of the daemon. This value goes from -20
> > # (most favorable scheduling) to 19 (least favorable). Using a
> > # negative value reduces the chances to lose state-change events.
>
> Perhaps it makes sense to factorize all of the conntrackd
> configuration examples in a single man page, let's say
> 'conntrackd.conf(5)'.
Absolutely, a manpage is good to have.
next prev parent reply other threads:[~2015-11-13 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 10:59 [conntrackd PATCH v3] conntrackd: add systemd support Arturo Borrero Gonzalez
2015-11-13 11:39 ` Arturo Borrero Gonzalez
2015-11-13 15:54 ` Pablo Neira Ayuso [this message]
2015-11-16 10:54 ` Arturo Borrero Gonzalez
2015-11-16 11:31 ` Pablo Neira Ayuso
2015-11-16 11:17 ` Pablo Neira Ayuso
2015-11-16 14:22 ` Arturo Borrero Gonzalez
2015-11-16 17:03 ` Pablo Neira Ayuso
2015-11-17 10:25 ` Pablo Neira Ayuso
2015-11-18 16:50 ` Arturo Borrero Gonzalez
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=20151113155431.GA1353@salvia \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--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.