[Oisf-users] suricatasc & suricata-update
Francis Trudeau
trudeauf at gmail.com
Thu May 7 23:45:48 UTC 2020
suricatasc can be told which socket to operate on, which is more granular
if you have multiple suricata processes running. killall would hit all the
suricata processes which might not be what you want. I'm sure there is
ways to target the correct process with killall (or pkill) but I think
that's more error prone and more of a hack.
On Thu, May 7, 2020 at 12:39 PM Cloherty, Sean E <scloherty at mitre.org>
wrote:
> Hi –
>
>
>
> Reviewing the documentation for Suricata Update and was wondering about
> using – suricatasc -c ruleset-reload-rules instead of killall -USR2. Any
> pros or cons to either approach?
>
>
>
>
>
> *Sean E. Cloherty*
>
> Lead Infosec Engineer / Scientist
>
> T211 - MITRE InfoSec
>
> 781-271-3707
>
> *MITRE* | Solving Problems for a Safer World
>
>
> _______________________________________________
> Suricata IDS Users mailing list: oisf-users at openinfosecfoundation.org
> Site: http://suricata-ids.org | Support: https://suricata-ids.org/support/
> List: https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users
>
> Forum: https://forum.suricata.io
> Trainings: https://suricata-ids.org/training/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20200507/ce046eae/attachment.html>
More information about the Oisf-users
mailing list