Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Duplicate
-
10.1
-
None
Description
While implementing systemd packaging part for MariaDB 10.1 in Debian and while comparing to MySQL 5.7 in Debian/Ubuntu, I noticed that the mysql.service file recommends against using `Restart=on-failure` and instead suggests `on-abort`:
mysql-server-5.7.mysql.service
|
# MySQL systemd service file
|
|
|
[Unit]
|
Description=MySQL Community Server
|
After=network.target
|
|
|
[Install]
|
WantedBy=multi-user.target
|
|
|
[Service]
|
User=mysql
|
Group=mysql
|
PermissionsStartOnly=true
|
ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
|
ExecStart=/usr/sbin/mysqld
|
ExecStartPost=/usr/share/mysql/mysql-systemd-start post
|
TimeoutSec=600
|
Restart=on-failure
|
RuntimeDirectory=mysqld
|
RuntimeDirectoryMode=755
|
(File can be viewed at https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/tree/debian)
Should we also in MariaDB have `on-abort`?
Comments danblack svoj ?
What about the RuntimeDirectory options MySQL 5.7 used in Debian/Ubuntu, should we have them too?
RuntimeDirectory=mysqld
|
RuntimeDirectoryMode=755
|