Doug Burks db4f138a78 FIX: surilogcompress cron job not running ...

The suricata user was originally created with `/opt/so/conf/suricata` as its home directory. I think at some point we changed permissions on `/opt/so/conf` and at that point the `surilogcompress` cron job stopped working. Changing the home directory to `/nsm/suricata` works on all of my PROD systems (including Ubuntu and CentOS).

For more information, please see:
https://github.com/Security-Onion-Solutions/securityonion/issues/7133

2022-03-15 07:10:02 -04:00

..

cron

Update copyright pattern to match other repos

2022-01-24 10:09:23 -05:00

files

Delete suri-rotate.conf

2021-01-22 10:08:23 +09:00

afpacket.map.jinja

Match max-pending-packets size

2020-11-02 08:38:45 -05:00

defaults.yaml

Pull in Suricata changes

2021-02-19 11:01:15 -05:00

init.sls

FIX: surilogcompress cron job not running

2022-03-15 07:10:02 -04:00

manager.sls

change how we allow or disallow states to be run https://github.com/Security-Onion-Solutions/securityonion/issues/2679

2021-01-20 15:09:53 -05:00

map.jinja

Add support for disabling Zeek and Suricata

2021-09-17 13:01:50 -04:00

suricata_config.map.jinja

Pull in Suricata changes

2021-02-19 11:01:15 -05:00

suricata_meta.yaml

Several Suricata things

2021-07-21 09:10:33 -04:00

threading.map.jinja

Update threading.map.jinja

2021-04-21 11:49:29 -04:00