Feature #15402
open
A new approach to rc.start_packages
0%
Description
I have been facing some issues with NUT package due to rc.start_packages.
Once an interfaces goes down, NUT restarts along with the other packages and this causes NUT to lose communication with the UPS.
A new approach to rc.start_packages, such as for an example, a tick option to select which packages should be restarted in a interface up/down event would helpful.
Not only NUT would benefit from it, but the entire device with less CPU cycles during this event, making things smoother.
Thank you
Updated by Jim Pingle 14 days ago
- Project changed from pfSense Plus to pfSense
- Category changed from Interfaces to Package System
- Priority changed from Low to Very Low
It might be viable but you have the logic a bit backward. The base system should not have specific knowledge of any package in this way, but it might be able to provide a plugin call where a package can declare for itself whether or not it wants to restart in these cases.
The main problem you have then is the package start/stop code is the same for boot time, interface events, gateway events, etc. Sometimes it's necessary to restart a package to pick up on interface changes even if it appears to be the same before/after. So it may take some experimentation with each package and each event type to know for sure what is safe.