mvc: setFormData / tokenize - it looks like targetNode.tokenize2().trigger('tokenize:clear'); fires a change event for all items in the list, since we hook the tokenizers via formatTokenizersUI() later, we can safely drop the event here to avoid an event storm. closes https://github.com/opnsense/core/issues/9408
(cherry picked from commit 31278f220894d1414ffa14b934afc99f137d1230)
mvc: setFormData / tokenize - it looks like targetNode.tokenize2().trigger('tokenize:clear'); fires a change event for all items in the list, since we hook the tokenizers via formatTokenizersUI() later, we can safely drop the event here to avoid an event storm. closes https://github.com/opnsense/core/issues/9408
system: simplify this powerd use
Killing something is as expensive as looking for it so we can
just use our normal approach here and simplify this spot. The
'killall' appears to be overkill anyway.
backend: remove spurious comments
This was a convenience trick when we started doing it but
it's now the fabric of how these types of command functions
work.
(cherry picked from commit 29180c9acb734f458f8c3c0b7c89e97f93c66a53)
backend: remove spurious comments
This was a convenience trick when we started doing it but
it's now the fabric of how these types of command functions
work.
backend: extend mwexecfb() to take pidfile and/or logfile
This allows to hide the daemon command completely making the calls
look like normal mwexecf() invokes.
interfaces: interface_carp_configure() conversion
The use of str_replace+addslashes+escapeshellarg is very odd:
https://github.com/pfsense/pfsense/commit/942fdd555964d48https://redmine.pfsense.org/issues/213
To avoid bugs leave this for now. escapeshellarg should be able
to handle this on its own. The password parsing is not more special
than anything else passed to the command line unless there is a bug
somewhere else which I doubt.