|author||Arturo Borrero Gonzalez <email@example.com>||2018-04-16 19:28:44 +0200|
|committer||Pablo Neira Ayuso <firstname.lastname@example.org>||2018-04-18 15:57:40 +0200|
systemd: default to use libsystemd if build with support for it
We may assume that if an user does build conntrackd with such feature, is with the intention to use it. So, if that's the case, default to use it. This eases some downstream use cases when dealing with default configs to be shipped to final users. This could be a mid-point solution, given some users are asking for a full revert of commit c01d0d9138112ec95ee316385ea2687dd94fa4e3. Signed-off-by: Arturo Borrero Gonzalez <email@example.com> Signed-off-by: Pablo Neira Ayuso <firstname.lastname@example.org>
Diffstat (limited to 'conntrackd.8')
1 files changed, 1 insertions, 4 deletions
diff --git a/conntrackd.8 b/conntrackd.8
index 6ccf261..de1e80c 100644
@@ -1,4 +1,4 @@
-.TH CONNTRACKD 8 "Aug 30, 2016" "" ""
+.TH CONNTRACKD 8 "Apr 16, 2018" "" ""
.\" Man page written by Pablo Neira Ayuso <email@example.com> (Dec 2007)
@@ -149,9 +149,6 @@ the configuration file, ignore this notice.
Starting with the 1.4.4 release, \fBconntrackd\fP includes integration with
\fBsystemd(1)\fP to use an unit file of \fIType=notify\fP and watchdog support.
-The daemon should be configured at build time to include such support
-and \fBconntrackd.conf(5)\fP should contain \fBSystemd on\fP.
During the 0.9.9 development, some important changes in the replication message
format were introduced. Therefore, \fBconntrackd\fP >= 0.9.9 will not work