Our Omada Application on Rocky Linux 8.10 (Giada Mi-NAS25 Motherboard) seem to go in a infinite dead loop occupying full CPU and cannot come out of it, until Omada is killed and restarted. We notice...

@Vincent-TP: What is the Dynamic memory footprint when upgrading from version v5.15.24.19 (or any v5 version) to v6 ? Also the Mobile app We are using is 4.5.27. I read that the V6 version needs v5...

The Change -Xms512m -Xmx512m was slow to work with and not stable (the controller would go in some sort of dead loop with 100% CPU usage) if we use the mobile app too much. So I increased to -Xms768m...

Finally got ir working with this Unit file script: [Unit] Description=Tp-Link Omada service startup After=network.target [Service] Type=forking WorkingDirectory=/opt/tplink/EAPController/bin/...

@Vincent-TP. Things did not go well as I expected to with this approach for the time being. Here is what happened: (1) System V Init cannot be disabled i think in Linux AFAIK as its a primary Init...

@Vincent-TP : Why Not ? I need a little time. I am now working on the SystemV Init to systemd startup configuration. The idea ther is to to somehow control the CPU usage of Omada when mangement task...