If mysqld_safe is invoked with the --syslog option, the errors are also logged in the system log (syslog). This feature works only if the system has the logger program, which is usually present on Linux systems, and in such cases, the daemon facility is used. By default, each syslog entry has a mysqld or mysqld_safe tag, depending on the program that generated its entry. If multiple instances of MariaDB (or MySQL) are running on the same system, it is advisable to add a different suffix for each instance to find out which particular instance logged a particular error. To do this, you can start mysqld_safe with the --syslog-tag option, as shown in the following example:

mysqld_safe --syslog --syslog-tag=serv1

In this case, the errors will be logged in the syslog, and the tags will be mysqld-serv1 and mysqld_safe-serv1. However, this option is usually set in the my.cnf file in the server's directory. In this case, the syslog and syslog_tag options must be written in the [mysqld_safe] options group, as shown in the following example:

[mysqld_safe]
syslog
syslog_tag=maria10

On Windows, there is no syslog, but errors are always recorded in the Windows Event Log in the Application log. This cannot be avoided. The source of entries is the name of the service or MySQL. Warnings, notes, and informational entries that do not follow the standard format are logged as informational messages.