Vojtěch Zeisek wrote:
Dne Ne 13. dubna 2014 14:58:22, Per Jessen napsal(a):
Vojtěch Zeisek wrote:
Dne Ne 13. dubna 2014 14:22:10, Per Jessen napsal(a):
Vojtěch Zeisek wrote:
Dne Ne 13. dubna 2014 13:26:35, Per Jessen napsal(a):
Vojtěch Zeisek wrote: > Dne Ne 13. dubna 2014 11:01:46, Per Jessen napsal(a): >> Vojtěch Zeisek wrote: Okay, but what does it say after a failed automatic mysql start-up? That ought to be the interesting one.
The same:
# systemctl enable mysql.service mysql.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig mysql on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: active (running) since So 2014-04-12 16:42:01 CEST; 22h ago
22 hours ago? So this was not a fresh reboot. If the info is going to be of any use, we need to see what happens when mysql is not started by systemd. -- Per Jessen, Zürich (14.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org