OPNsense plugin: can't change PROCESS_COUNT

[Arien02]

Hi all!

Every time a BW demanding task hit my network, the four sensor.py processes use all the available CPU time and network performance drops (around 40-50% in some scenarios).

I'm using OPNsense 25.7.3 with Maltrail, but due the high CPU load, I want to limit PROCESS_COUNT to 2 cores (out of the max 4 cores available), but the only way I've found is modifying maltrail.conf file manually, but as soon as the firewall reboots Maltrail service overwrites my config file and defaults again to "PROCESS_COUNT $CPU_CORES".

Is there any way to make this change permanent?
Thank you.

[MikhailKasimov]

Hello!

@mimugmail @juliocbc Could you check, please?

[MikhailKasimov]

UPD: BTW, by default, PROCESS_COUNT=1 : https://github.com/stamparm/maltrail/blob/master/maltrail.conf#L58

[juliocbc]

Yes sure! I will check and let you know about it!

[Arien02]

BTW I've found a trick to make this change work: editing /usr/local/opnsense/service/templates/OPNsense/Maltrail/maltrail.conf

Now each time sensor get restarted it loads the modified template and only one process is running and CPU load 99% for only one core.

Same behavior if you try to change server admin password, everytime OPNsense restarts the password is overwritted to template defaults.

Maybe the plugin can implement a way to make this persistent without modifying files in shell.

Greetings.