From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org, jengelh@inai.de
Subject: Re: [conntrackd PATCH v2] conntrackd: add basic systemd notification support
Date: Mon, 26 Oct 2015 21:12:36 +0100 [thread overview]
Message-ID: <20151026201236.GA13580@salvia> (raw)
In-Reply-To: <144524350598.16550.11699956757376724904.stgit@r2d2.cica.es>
Hi Arturo,
On Mon, Oct 19, 2015 at 10:33:15AM +0200, Arturo Borrero Gonzalez wrote:
> This patch adds a basic systemd notification support.
>
> Most of distros (Debian, RHEL, Ubuntu, ArchLinux...) use systemd as
> init system.
> Notifiying systemd that conntrackd is now running has many
> benefits, the main being users concatenating systemd services depending on
> the main conntrackd daemon being started.
>
> The systemd support means conntrackd will require libsystemd, so a
> configure swith is added:
>
> % ./configure --disable-systemd
>
> We can further integrate conntrackd with systemd:
> * add watchdog support
> * report daemon errors (f.e, errno codes)
> * tell systemd conntrackd PID
> * report about conntrackd Unix socket
Interesting. I would really like to see a patchset that adds one of
these features above at least. So I basically need more meat here...
Another comment below.
> diff --git a/configure.ac b/configure.ac
> index 70d3729..8bb9581 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -61,6 +61,9 @@ AC_ARG_ENABLE([cthelper],
> AC_ARG_ENABLE([cttimeout],
> AS_HELP_STRING([--disable-cttimeout], [Do not build timeout support]),
> [enable_cttimeout="no"], [enable_cttimeout="yes"])
I'd appreciate if you send me patches to fix these AC_ARG_ENABLE above
in first place.
Thanks!
prev parent reply other threads:[~2015-10-26 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 8:33 [conntrackd PATCH v2] conntrackd: add basic systemd notification support Arturo Borrero Gonzalez
2015-10-26 20:12 ` 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=20151026201236.GA13580@salvia \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--cc=jengelh@inai.de \
--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).