This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 190
Wrong behaviour of SIGHUP #75
Comments
On Sat, Mar 9, 2013 at 6:00 AM, Hosting Nuggets notifications@github.comwrote:
You can use a pid file to correctly kill the process and relaunch it. |
Thanks for the fast feedback. Hopefully the SIGHUP to refresh the config will soon be implemented. In the meantime I will write a wrapper script around pulledpork to restart Barnyard2 once its finished. |
binf
added a commit
to binf/barnyard2
that referenced
this issue
Apr 26, 2013
Add: Support for SIGHUP Fixed: Compile issue when debug was enabled (missing , in some DEBUG_WRAP code. Fixed: Changed a few places where the snort literal was used instead of barnyard2 and this could confuse some first time barnyard2 users. Fixed: RPM spec file to point to good version (when needed) Bumped: Build to 326 --github specific Fixes firnsy#81 Fixes firnsy#73 Fixes firnsy#75 Close firnsy#82 Close firnsy#83 Close firnsy#80 Close firnsy#79 Close firnsy#78 Close firnsy#27 --github specific
binf
added a commit
to binf/barnyard2
that referenced
this issue
Apr 26, 2013
Add: Support for proper signal handling. Fixed: Compile issue when debug was enabled (missing , in some DEBUG_WRAP code. Fixed: Changed a few places where the snort literal was used instead of barnyard2 and this could confuse some first time barnyard2 users. Fixed: RPM spec file to point to good version (when needed) Bumped: Build to 326 --github specific Fixes firnsy#81 Fixes firnsy#73 Fixes firnsy#75 Close firnsy#82 Close firnsy#83 Close firnsy#80 Close firnsy#79 Close firnsy#78 Close firnsy#27 --github specific
binf
added a commit
to binf/barnyard2
that referenced
this issue
May 9, 2013
Add: Support for proper signal handling. Add: README info for google mailing lists. Fixed: Compile issue when debug was enabled (missing , in some DEBUG_WRAP code. Fixed: Changed a few places where the snort literal was used instead of barnyard2 and this could confuse some first time barnyard2 users. Fixed: RPM spec file to point to good version (when needed) Bumped: Build to 326 --github specific Fixes firnsy#81 Fixes firnsy#73 Fixes firnsy#75 Close firnsy#82 Close firnsy#83 Close firnsy#80 Close firnsy#79 Close firnsy#78 Close firnsy#27 --github specific
binf
added a commit
to binf/barnyard2
that referenced
this issue
May 10, 2013
Add: Support for proper signal handling. Add: README info for google mailing lists. Fixed: Compile issue when debug was enabled (missing , in some DEBUG_WRAP code. Fixed: Changed a few places where the snort literal was used instead of barnyard2 and this could confuse some first time barnyard2 users. Fixed: RPM spec file to point to good version (when needed) Bumped: Build to 326 --github specific Fixes firnsy#81 Fixes firnsy#73 Fixes firnsy#75 Close firnsy#82 Close firnsy#83 Close firnsy#80 Close firnsy#79 Close firnsy#78 Close firnsy#27 --github specific
binf
added a commit
to binf/barnyard2
that referenced
this issue
Jun 16, 2013
Add: Support for proper signal handling. Add: README info for google mailing lists. Fixed: Compile issue when debug was enabled (missing , in some DEBUG_WRAP code. Fixed: Changed a few places where the snort literal was used instead of barnyard2 and this could confuse some first time barnyard2 users. Fixed: RPM spec file to point to good version (when needed) Bumped: Build to 326 --github specific Fixes firnsy#81 Fixes firnsy#73 Fixes firnsy#75 Close firnsy#82 Close firnsy#83 Close firnsy#80 Close firnsy#79 Close firnsy#78 Close firnsy#27 --github specific
eugpermar
pushed a commit
to redBorder/barnyard2
that referenced
this issue
Jul 4, 2013
Add: Support for proper signal handling. Add: README info for google mailing lists. Fixed: Compile issue when debug was enabled (missing , in some DEBUG_WRAP code. Fixed: Changed a few places where the snort literal was used instead of barnyard2 and this could confuse some first time barnyard2 users. Fixed: RPM spec file to point to good version (when needed) Bumped: Build to 326 --github specific Fixes firnsy#81 Fixes firnsy#73 Fixes firnsy#75 Close firnsy#82 Close firnsy#83 Close firnsy#80 Close firnsy#79 Close firnsy#78 Close firnsy#27 --github specific
netsiphon
pushed a commit
to netsiphon/barnyard2
that referenced
this issue
Oct 18, 2016
Add: Support for proper signal handling. Add: README info for google mailing lists. Fixed: Compile issue when debug was enabled (missing , in some DEBUG_WRAP code. Fixed: Changed a few places where the snort literal was used instead of barnyard2 and this could confuse some first time barnyard2 users. Fixed: RPM spec file to point to good version (when needed) Bumped: Build to 326 --github specific Fixes firnsy#81 Fixes firnsy#73 Fixes firnsy#75 Close firnsy#82 Close firnsy#83 Close firnsy#80 Close firnsy#79 Close firnsy#78 Close firnsy#27 --github specific
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SIGHUP in Baryard2 v2.1.12 terminates the barynard2 process, shouldn't it be reloading/refreshing the config files instead?
I am using pulledpork to send a SIGHUP to Snort and Barnyard2 after downloading the newest rules and as such Barnyard2 is not running anymore...
The text was updated successfully, but these errors were encountered: