Files
securityonion/salt
Josh Patterson 84cd966736 FIX: prevent so-sensor-clean runaway loop and concurrent instances
The cleanup loop had no progress check or pass limit, so once /nsm was over
threshold with nothing left to reclaim it spun at full speed, writing 1.1 GB /
12.5M lines to sensor_clean.log in five hours. Stop when a pass removes
nothing, when a pass frees no space, or at MAX_PASSES, and drop the per-pass
"no old files" logging in favor of one actionable line.

Replace the pgrep guard with flock -n. A find|while read subshell inherits the
parent's argv, so pgrep -cf counted one instance as hundreds; it was also
check-then-act, which let cron stack up overlapping runs.

Paths now derive from SENSOR_DIR with env-overridable LOG/LOCK so the
over-threshold path can be tested against a scratch filesystem.
2026-09-14 12:14:13 -04:00
..
2025-12-02 11:16:08 -06:00
…
2025-12-11 17:30:06 -05:00
2026-09-04 17:50:32 -04:00
2025-12-02 11:16:08 -06:00
2026-08-20 17:00:53 -05:00
2026-07-15 16:28:35 -04:00
2024-07-09 10:06:16 -04:00
2026-09-10 07:27:25 -04:00
2026-03-19 14:39:10 -04:00
2026-09-11 10:54:20 -06:00
2026-01-07 14:14:57 -05:00
2025-10-14 11:03:00 -04:00
2025-08-04 15:25:26 -04:00
2026-08-14 16:04:48 -04:00