Also refer to the service file for startup.

Also include the ftp.mariadb.org script rather than old name.

This turns out to be a too expensive call to use for every freed page,
especially under global buffer pool mutex protection.

Also, the usefulness of proactive shrinking of the buffer pool on Windows
this is seems questionable - there is no OOM killer, and the OS will
shrink working sets itself.

This fixes up 25b91c3f

galera_sr.GCF-1060 'innodb'              w2 [ fail ]  timeout after 900 seconds

galera_3nodes.galera_ssl_reload At line 50: mysql_shutdown failed
galera_3nodes.galera_ssl_reload : MDEV-30172 At line 50: mysql_shutdown failed
galera_3nodes.GCF-354 : mysqltest: At line 39: query 'DROP TABLE test.t1' failed: 1047: WSREP has not yet prepared node for application use
galera_3nodes.GCF-354 : mysqltest: At line 30: query 'INSERT INTO test.t1 values (1)' failed: 1180: Got error 6 "No such device or address"

galera_wan : [ERROR] WSREP: /home/buildbot/buildbot/build/gcs/src/gcs_state_msg.cpp:gcs_state_msg_get_quorum():947: Failed to establish quorum.

Merge Jan's bb-10.6-merge-jan branch:

MDEV-30172 Galera test case cleanup

    * Delete tests that are not supported and not going to be supported
      any time soon
    * Fix result set on tests that are not run on bb
    * Fix tests that fail because of auto increment offset
    * Make sure that disabled tests have open bug report

galera.galera_bf_abort_at_after_statement disabled by Daniel Black

Adjust galera/galera_3nodes disabled tests.

Hide the errors related to missing innodb stats tables in bootstrap mode
on the assumption that because we are in bootstrap mode they are going
to be created.

mtr_t::commit_file(): Protect the rename operation with fil_system.mutex
like we used to do before commit 2e43af69
in order to prevent fil_node_open_file() from running concurrently.
In other words, fil_system.mutex will protect the consistency of
fil_node_t::name and the file name in the file system.

This race condition should be very hard to trigger. We would need
a low value of innodb_open_files or table_cache limit so that
fil_space_t::try_to_close() will be invoked frequently. Simultaneously
with a RENAME operation, something (such as a write of a data page)
would have to try to open the file.

This fixes up commit dd5f4b36