-
Jens Even Berg Blomsoy authored
SERVICE NAME ON WINDOWS Problem: During creation of "WL9809 - RESTART command" the bug was introduced. Starting the child process creates a separate instance of mysqld.exe and the first instance does the setup for Windows Service. The setup was not transfered to the child instance, thus creating the situation where the child process does not even know it is running as a service, and will skip everything related to the service code. This caused the parameters in the my.ini and my.cnf files to be ignored, when starting as a service. Only the default service names (mysqld, mysql_cluster, server, mysqld-8.0) could load different parameters from the my.ini file Solution: The patch makes the monitor process transfer all the arguments given from the command line, to the child process. It also makes the child process detect if its parent process is a Windows Service.
Jens Even Berg Blomsoy authoredSERVICE NAME ON WINDOWS Problem: During creation of "WL9809 - RESTART command" the bug was introduced. Starting the child process creates a separate instance of mysqld.exe and the first instance does the setup for Windows Service. The setup was not transfered to the child instance, thus creating the situation where the child process does not even know it is running as a service, and will skip everything related to the service code. This caused the parameters in the my.ini and my.cnf files to be ignored, when starting as a service. Only the default service names (mysqld, mysql_cluster, server, mysqld-8.0) could load different parameters from the my.ini file Solution: The patch makes the monitor process transfer all the arguments given from the command line, to the child process. It also makes the child process detect if its parent process is a Windows Service.
Loading