If the CN is already an FQDN on the given domain, this prevents the
domain from being present in the record twice (e.g. host.example.com
as a CN leads to records for host.example.com.example.com)
* Rename local_sync_accounts() to local_reset_accounts() and keep it
only being used /etc/rc.bootup
* Reimplement local_sync_accounts() receiving a list of users and
groups to be added and/or deleted
* Remove call to filter_configure xmlrpc method from
rc.filter_synchronize since it's now called internally from
restore_config_section.
* On restore_config_section implementation stop copying all content
from user/group sections. Instead check for new/modified/deleted
items and create necessary arrays to be passed to local_syng_accounts
* Add a parameter to filter_configure xmlrpc method to decide when to
call a full reset of users/groups using local_reset_accounts()
Allow "Both" to be selected for IPv4/IPv6 on IPsec P1, in the config use both addresses as "left =" if they both exist.
Some cases where a single address was assumed (e.g. ping hosts) default to using the first address.
Doesn't make sense when selecting a VIP that is a single type, but should still handle that gracefully, only using the one that actually exists.
There might be some edge cases that this doesn't handle properly.
It will use the ceil() function to always use the ceiling after loading a config.
Also onchange of bandwidth will call the ceil function to put in a whole number.
On d9b05eb490 the way aliases containing a mix of IP address and FQDNs
works has changed and all items were added to filterdns to make sure
the pf table created would be persistent. The flag $use_filterdns was
being set only when the array item used to control didn't exist yet.
Because of that, the second call to the same function made it to return
a different result. Set it independent if a new array item is created
or not to make the function to properly return the right thing.
