It applies all sysctls on interfaces settings save but there
isn't much of a point splitting the functionality or hardcoding
yet another spot with the required sysctls.
In a future version we might want to be able to ship metadata per log view, in which case the service binding and defaults should be provided from there.
/etc/ttys has two more entries one of which we add conditionally
and the other one we don't need so for now don't add these two.
When we rework the code in system.inc we can include them later
in the new way.
Suspicion confirmed that e.g. 6RD misses the wrong interface.
Just run the code when necessary instead of caching it for
a situation that isn't matching.
Since /boot/efi is the default in FreeBSD 13 and will be
auto-mounted through /etc/fstab it makes sense to show it
in the dashboard as an active partition.
This sort of completes the previous effort to improve the
sysctl handling. The idea to embed sysctls into the config.xml
is certainly valid, but for some values we needed more leeway
for system defaults and changing them over time, which lead
to this state where we can drop config.xml default tunables
since the system will now apply and display then for the same
visibility but offer less incentive to change these values.
One thing missing here is adding a system tunable override
(plus sign) for system values, but we shall deal with this later
because for now they can always be added manually by copy+paste.
Currently, when configured, "strict-order" adds the necessary "strict-order" argument. However, the hardcoded "all-servers" arguments overrides this, making "strict-order" pointless.
With this change, "all-servers" and "strict-order" are mutually exclusive.
Originally looked into
Starting API dispatcher
2021-12-22 11:03:56: (configfile.c.426) Warning: mod_auth should be listed in server.modules before dynamic backends such as mod_cgi
2021-12-22 11:03:56: (configfile.c.426) Warning: mod_auth should be listed in server.modules before dynamic backends such as mod_fastcgi
but it looks like this is a false positive since we don't have mod_auth in there.
This formatted number is used by the Interface Statistics widget,
and makes the columns go wider than necessary when going above a
terabyte of data. Add petabytes for good measure.
Although a direct table lookup will be faster than using a lookup in isAlias(), it's likely not problematic to have a slightly slower lookup using is_alias(), but if performance is of the essence at some point we can easily cache results in isAlias() to reach the same target.
