Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*
Posted by
Gnomad on
Jul 02, 2019; 7:11am
URL: https://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1792.html
Sounds reasonable! The original shield luci had a page showing all the custom crons - is that something you've pulled over?
If so, people can always tweak the timing to their own requirements anyway.
Note that (from memory) not all shield models have the MMC slot, and for other users an MMC card might not be inserted - so you'll want an availability detection check upfront regardless.
On Tue, 2 Jul 2019 at 15:05, Grommish [via Itus Networks Owners Forum] <
[hidden email]> wrote:
One of the reasons I was looking into the F2FS (Flash Friendly File System) was because it incorporates wear-leveling, which helps with the destructive writes shortening the life.
Currently, I am moving the alert.fast.xxxx files (1mb each) to /etc/snort/logs, pulling out the Priority 1 logs and saving them on disk, then removing everything but the last 5 logs (by timestamp). I'm crontab'ing this every half an hour. You're right about the logs getting get many and large quickly, and I understand the concern.
What about this..
Every 30 minutes, pulling the Priority 1 alerts/drops out and storing that on disk, but instead of moving/removing the alert.fast.xxxx files, just removing all but the "newest" 4 (not counting the active alert.fast file) to keep the RAM from getting filled up.
This way, we can remove almost all of the MMC writes AND free up RAM.
Thoughts on this strategy?
To unsubscribe from [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*,
click here.
NAML
OpenWrt SNAPSHOT, r10391-3d8d528939