Team Speak 3 server V.3.8.0

=== Server Release 3.8.0 28 May 2019

Important: This release requires GNU C library (glibc) 2.17 or later on Linux. If you need to
           check which version of glibc is installed on your system, you can use `ldd --version`,
           which usually comes with any glibc installation.
Important: Client badge information is now signed to prevent using fake data. Badges in the old
           format will not be visible on this server.
           TeamSpeak Client version 3.3.0 with support for signed badges will be available soon.

Added: The query command `banlist` now supports optional pagination parameters.
       Please refer to the ServerQuery documentation for details.
Added: Temporary passwords are now stored in the database and will be loaded on start.
Added: New command line parameters 'daemon' and 'pid_file'. This makes it possible
       to start the server as a daemon.
Added: Channel properties and permissions to support channel banners.
       This feature requires TeamSpeak Client version 5.

Changed: The startscript restart parameter now allows to use more than one parameter.
Changed: New server logs are no longer created with a BOM.
Changed: Server / channel icons will not display as negative values anymore in ServerQuery.
Changed: ServerQuery commands `clientlist -ip` and `clientinfo` won't display brackets around IPv6
         addresses of clients anymore.
Changed: Max size of text messages has been increased to 8 KiB for improved usability in upcoming
         TeamSpeak Client releases.

Fixed: Reduced packet loss on systems under high load.
Fixed: In some rare case the server did crash when shutting down a virtual server.
Fixed: The startscript restart parameter could not be used when ran outside the server directory.
Fixed: Server did report the ability to create channels to the weblist in cases where a client
       could not create any channel.
Fixed: No more 'Error querying client connection info: 1796' messages in the client log.
Fixed: Server freezes related to heavy server usage.
Fixed: Critical log messages on startup do not create cores.