interfaces: parse ifconfig output despite exit error in legacy_interfaces_details()
Move stderr to /dev/null and always read stdout. It improves intermittent
issues with ifconfig that will return data but "fail" with a non-zero return
code.
PR: https://github.com/opnsense/src/issues/284
Suggested by: @e-alfred
widgets: enhance Live Log widget (#10086)
Uses client-side DOM for determining log endpoints, doesn't require any default target access, allows options for severity and search filter and variable log lines to show, which are displayed in summary in widget, and uses true log tailing plus backfill
---------
Co-authored-by: Stephan de Wit <stephan.de.wit at deciso.com>
interfaces: parse ifconfig output despite exit error in legacy_interfaces_details()
PR: https://github.com/opnsense/src/issues/284
In this version print the error number and stderr output. We'd like to know
which part of ifconfig fails and don't want to taint the parser output. If
it's empty it's empty anyway. But maybe in the commit we merge we should just
ditch everything to /dev/null as we do mute the error in most cases anyway.
The resulting array is empty worst case which is just what it is.
Suggested by: @e-alfred
interfaces: parse ifconfig output despite exit error in legacy_interfaces_details()
PR: https://github.com/opnsense/src/issues/284
In this version print the error number and stderr output. We'd like to know
which part of ifconfig fails and don't want to taint the parser output. If
it's empty it's empty anyway.
Suggested by: @e-alfred
