From: "Slawek Lis" <slis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/suricata/files/
Date: Mon, 16 Jan 2017 12:28:00 +0000 (UTC) [thread overview]
Message-ID: <1484569674.52c57d2e8707113c2b019013c83706b584b59bc7.slis@gentoo> (raw)
commit: 52c57d2e8707113c2b019013c83706b584b59bc7
Author: Slawomir Lis <slis <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 16 12:27:54 2017 +0000
Commit: Slawek Lis <slis <AT> gentoo <DOT> org>
CommitDate: Mon Jan 16 12:27:54 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=52c57d2e
net-analyzer/suricata: updated config file
Bug report: #605754
Package-Manager: Portage-2.3.3, Repoman-2.3.1
net-analyzer/suricata/files/suricata-3.2-conf | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/net-analyzer/suricata/files/suricata-3.2-conf b/net-analyzer/suricata/files/suricata-3.2-conf
index d8466b4..655b947 100644
--- a/net-analyzer/suricata/files/suricata-3.2-conf
+++ b/net-analyzer/suricata/files/suricata-3.2-conf
@@ -54,3 +54,9 @@ SURICATA_OPTS="-i eth0"
# SURICATA_GROUP_q1="suricata"
# SURICATA_USER="suricata"
# SURICATA_GROUP="suricata"
+
+# Suricata processes can take a long time to shut down.
+# If necessary, adjust timeout in seconds to be used when calling stop from the init script.
+# Examples:
+# SURICATA_MAX_WAIT_ON_STOP="300"
+# SURICATA_MAX_WAIT_ON_STOP="SIGTERM/30"
next reply other threads:[~2017-01-16 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 12:28 Slawek Lis [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-22 11:51 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/suricata/files/ Marek Szuba
2019-12-17 0:16 Marek Szuba
2018-01-24 7:26 Slawek Lis
2018-01-23 18:57 Slawek Lis
2017-01-16 12:25 Slawek Lis
2017-01-09 7:22 Slawek Lis
2016-12-30 7:50 Slawek Lis
2016-12-29 6:23 Slawek Lis
2016-12-27 10:43 Slawek Lis
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=1484569674.52c57d2e8707113c2b019013c83706b584b59bc7.slis@gentoo \
--to=slis@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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