You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can be done however if pfdetect goes from disabled -> enabled or enabled -> disabled, pfqueue must be restarted to ensure the pfdetect worker is started or stopped.
If that is ok then yes this can be done quickly.
If not then I would need to add some type of polling to the pfqueue master to pickup on configuration changes.
I'd say it would be OK for pfqueue to be restarted, it should use the isManaged sub of pfdetect since it contains custom logic. And we need to document the pfqueue restart in the admin guide in places where we enable pfdetect
Do we really need to spawn a (or whatever configured number of) pfqueue for pfdetect if pfdetect is not running ?
The text was updated successfully, but these errors were encountered: